Detection and reporting of keepalive messages for optimization of keepalive traffic in a mobile network

ABSTRACT

Detection of network transactions or keepalives for maintaining long lived connections are disclosed. A keepalive detector can detect keepalive traffic based on keepalive parameters determined from an analysis of socket level network communication log data that record data transfer events including data sent from mobile applications or clients on a mobile device and data received by the mobile applications or clients on the mobile device, timing characteristics, protocol types, etc. Various statistical analyses can be performed on the network communication data to detect keepalives, taking into account variability in intervals of the data transfer events and sizes of data sent and received on each event. The keepalive detector can also detect keepalives from stream data on a mobile device by analyzing socket level communication messages including timing characteristics and amount of data transferred to detect keepalives and report keepalives using a data structure.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Utility patentapplication Ser. No. 15/443,424 titled “DETECTION AND REPORTING OFKEEPALIVE MESSAGES FOR OPTIMIZATION OF KEEPALIVE TRAFFIC IN A MOBILENETWORK” filed on Feb. 27, 2017, which is a continuation of U.S. Utilitypatent application Ser. No. 15/051,609 titled “DETECTION AND REPORTINGOF KEEPALIVE MESSAGES FOR OPTIMIZATION OF KEEPALIVE TRAFFIC IN A MOBILENETWORK” filed on Feb. 23, 2016, now U.S. Pat. No. 9,591,688 issued Mar.7, 2017, and is a continuation of U.S. Utility patent application Ser.No. 14/266,759 titled “DETECTION AND REPORTING OF KEEPALIVE MESSAGES FOROPTIMIZATION OF KEEPALIVE TRAFFIC IN A MOBILE NETWORK” filed on Apr. 30,2014, now U.S. Pat. No. 9,271,325 issued Feb. 23, 2016, which claimspriority to and benefit from U.S. Provisional Patent Application Ser.No. 61/817,718 titled “OPTIMIZATION OF NON-USER INTERACTIVE TRAFFIC IN AMOBILE NETWORK BY KEEP ALIVE IDENTIFICATION AND DELAY TOLERANCE OF KEEPALIVE MESSAGES AND OTHER NON-USER INTERACTIVE TRAFFIC” filed on Apr. 30,2013; U.S. Provisional Patent Application Ser. No. 61/823,340 titled“IDENTIFICATION AND REPORTING OF KEEP-ALIVE MESSAGES AND OTHER NON-USERINTERACTIVE TRAFFIC IN A MOBILE NETWORK” filed on May 14, 2013; and U.S.Provisional Patent Application Ser. No. 61/836,039 titled“IDENTIFICATION AND REPORTING OF KEEP-ALIVE MESSAGES AND OTHER NON-USERINTERACTIVE TRAFFIC IN A MOBILE NETWORK” filed on Jun. 17, 2013. Theentire content of the aforementioned applications are expresslyincorporated by reference herein.

BACKGROUND

When a connection is established between a client and a server, the twoentities dedicate a portion of their resources to the connection.Typically, after a data transfer session is completed, the connectionbetween the client and the server is terminated by the client or theserver by sending an IP packet (e.g., FIN packet). However, sometimesthe client and the server can maintain the connection by using keepalivemessages or heartbeat messages. A keepalive message can be sent anentity at one end of a connection to check the operational status ofanother entity at the other end of the connection. When the receivingentity receives a keepalive message from a sending entity, the receivingentity immediately replies with an acknowledgment message, therebyinforming the sending entity that it is alive or operational. If,however, the sending entity does not receive an acknowledgement messagefor a period of time, the sending entity can terminate the connection.

The keepalive messages from these always-on applications allow theapplications to receive messages with less delay. However, thisimprovement in latency has associated costs. These costs includeconsumption of a significant amount of energy in mobile devices,additional signaling in the mobile network and bandwidth consumption.For example, to be able to send keepalive messages frequently, a mobiledevice needs to frequently transition its radio between a high poweredstate and an idle state or remain in a high powered state instead of theidle state for a longer period of time, resulting in fast draining ofbattery. These radio transitions also cause additional signaling in thenetworks as radio resource control (RRC) messages need to be exchangedbetween the mobile device and base station to establish a radio link.Furthermore, each keepalive message can be as large as 20-60 bytes insize, and a large number of such keepalive messages from multipleapplication can add up to consume a substantial chunk of the networkbandwidth. Thus keepalive optimization is desired. However, keepaliveoptimization can occur only when keepalives can be accurately detected.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts an example of data sent or received by mobileapplications on a mobile device using utilizing various proprietary,non-proprietary and/or encrypting protocols read from a TransportControl Protocol (TCP) stream for detecting and optimizing keepalivetraffic in a mobile network.

FIG. 1B depicts an example diagram of a system where a host serverfacilitates management of traffic, content caching, and/or resourceconservation between mobile devices (e.g., wireless devices), anapplication server or content provider, or other servers such as an adserver, promotional content server, or an e-coupon server in a wirelessnetwork (or broadband network) for resource conservation. The hostserver can further determine parameters that can be used in identifyingkeepalives from a TCP stream for optimizing keepalive traffic in amobile network.

FIG. 1C depicts an example diagram of a proxy and cache systemdistributed between the host server and device which facilitates networktraffic management between a device, an application server or contentprovider, or other servers such as an ad server, promotional contentserver, or an e-coupon server for resource conservation and contentcaching. The proxy system distributed among the host server and thedevice can further identify keepalives from a TCP stream on the mobiledevice for optimizing keepalive traffic in a mobile network.

FIG. 1D depicts an example diagram of the logical architecture of adistributed proxy and cache system.

FIG. 1E depicts an example diagram showing the architecture of clientside components in a distributed proxy and cache system.

FIG. 1F depicts a diagram of the example components on the server sideof the distributed proxy and cache system.

FIG. 2A depicts a block diagram illustrating another example ofclient-side components in a distributed proxy and cache system, furtherincluding a keepalive detector that can identify keepalives from a TCPstream.

FIG. 2B depicts a block diagram illustrating additional components inthe local proxy shown in the example of FIG. 2A.

FIG. 2C depicts a block diagram illustrating additional components inthe proprietary/non-standard protocol adaptation engine shown in theexample of FIG. 2A.

FIG. 3 depicts a block diagram illustrating additional components in thekeepalive detector shown in the example of FIG. 2A.

FIG. 4A depicts a block diagram illustrating an example of server-sidecomponents in a distributed proxy and cache system, further including akeepalive detector that can identify keepalives from a TCP stream and aproprietary/non-standard protocol adaptation engine.

FIG. 4B depicts a block diagram illustrating additional components inthe keepalive detector shown in the example of FIG. 4A.

FIG. 4C depicts a block diagram illustrating additional components inthe proprietary/non-standard protocol adaptation engine shown in theexample of FIG. 2A.

FIG. 5 depicts a logic flow diagram illustrating an example method ofanalyzing socket level network communication log data using statisticalanalyses to identify regular interval and regular byte sizescorresponding of keepalives originating from an application.

FIG. 6 depicts a logic flow diagram illustrating an example method ofperforming a statistical analysis on a pattern of data sent and receivedto determine a regular interval for the pattern.

FIG. 7 depicts a logic flow diagram illustrating an example method ofperforming statistical analyses on a pattern of data sent and receivedto determine regular byte sizes for the pattern.

FIG. 8 depicts a logic flow diagram illustrating an example method ofmonitoring a TCP stream of data sent and received by the application andidentifying keepalives from the TCP stream when the same TCP streamincludes regular byte sized data sent and received at regular intervals.

FIG. 9 depicts a logic flow diagram illustrating an example method ofusing timing characteristics and an amount of data sent and received toidentify whether a connection or TCP stream contains a keepalive andreporting the detection of the keepalive.

FIG. 10 depicts a diagrammatic representation of a machine in theexample form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification including examples of any termsdiscussed herein is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions will control.

Embodiments of the present disclosure include technology for detectingor identifying keepalive messages (“keepalives”) from Transport ControlProtocol (TCP) streams in a mobile network (hereinafter “keepalivedetection technology”).

Existing systems and methods can optimize mobile traffic over standardand non-proprietary application level protocols including, but notlimited to: Hypertext Transfer Protocol (HTTP), Hypertext TransferProtocol Secure (HTTPS), File Transfer Protocol (FTP), Simple MailTransfer Protocol (SMTP), Internet Message Access Protocol (IMAP), PostOffice Protocol (POP), and the like. However, many mobile applicationsare moving away from the standard protocols towards vendor specificproprietary protocols. For example, Google utilizes a non-standardTransmission Control Protocol (TCP) port 5228. By way of anotherexample, the “WhatsApp” mobile application uses a customized version ofthe Extensible Messaging and Presence Protocol (XMPP). Similarly, someapplications such as Skype and Yahoo mail use their own proprietaryprotocols, while others such as Urban Airship's push notificationsprotocol is used by various vendors.

Typically, to perform any detection and optimization of traffic such askeepalive traffic, non-interactive traffic or other user interactivetraffic, the protocols must be well understood. For example, the headerand other protocol specific data must be known before any optimizationcan be performed. As proprietary protocols are not standardized and notwell understood, mobile traffic over such proprietary protocols cannotbe optimized by existing optimization systems and methods. The disclosedtechnology can identify keepalives from the TCP streams regardless ofthe application level protocols used by the applications from where thekeepalives originate and enable optimization of the keepalives. Thus,the disclosed keepalive detection technology provides a protocolagnostic technology for identifying keepalives for optimization.Optimization of the keepalives in a wireless or mobile network conservesthe resources on mobile devices and/or the server by reducing signaling,number of unnecessary radio transitions (powering up or powering down)and battery drain. In some embodiments, the keepalive detectiontechnology can identify traffic that includes keepalive and excludespayload traffic or other higher safety scenarios to engage in keepaliveoptimization.

In some embodiments, the keepalive detection technology can be used tocategorize mobile transactions as transactions associated with (a)keepalives; (b) other non-interactive traffic; and (c) interactivetraffic to facilitate management and conservation of traffic in mobilenetworks.

In some embodiments, the keepalive detection technology utilizesTransport Control Protocol (TCP) streaming optimization along with alocal proxy and/or a proxy server of a distributed proxy system toidentify transactions within a TCP stream. The keepalive detectiontechnology includes categorization of those transactions to (a)keepalives; (b) other non-interactive traffic; and (c) interactivetraffic.

In some embodiments, the keepalive detection technology can identifynetwork transactions (e.g., keepalives) based on a combination ofparameters, such as but not limited to: periodicity or intervals, sizethresholds, similar/repeating content, content following a certainpattern (e.g., content having an incrementing or decrementing portion orcounter) and/or based on knowledge of the actual application levelprotocol. In some embodiments, non-interactive traffic and interactivetraffic can be distinguished from each other by proxies of useractivity, a status of the application performing the data transfer(e.g., foreground, background, active, non-active), status of outputmechanisms, such as screen, audio, notification LED, Bluetooth, NFC,RFID, touch sensor, any other types of sensors, camera, etc., readingsfrom the any other sensors or detectors of the device, such asmicrophone, accelerometer, biosensors, location sensors, motion sensors,etc., or a combination thereof.

In some embodiments, some applications and servers send small sizedinformation back and forth in regular interval to keep their TCPconnection alive. These information can recorded in a log. The keepalivedetection technology can detect or identify keepalives based on ananalysis of socket level network communication log data (“netlog”). FIG.1A depicts an example table 100A of data sent or received by mobileapplications on a mobile device using utilizing various proprietary,non-proprietary and/or encrypting protocols read from a TransportControl Protocol (TCP) stream and recorded in a netlog for detecting andoptimizing keepalive traffic in a mobile network. The table 100A caninclude various fields of information such as application names 180, thedata sent from the application to the network (e.g., sendbytes orfromapp bytes 181), the data received by the application from thenetwork (e.g., recbytes or fromnet bytes 182), the host names of theapplication servers associated with the applications, theapplication-level protocol 183, port numbers, number of occurrences 184(e.g., the number of times that the same or similar sized bytes of datafrom sent and received), the median interval 186 (e.g., median of theintervals between each of the occurrences 184) and the mean interval.

In many instances, there can be ambiguities in the recorded netlog datathat can prevent accurate detection of keepalives. One example ambiguityis the keepalive interval (i.e., the time period between twokeepalives). The interval at which the information is sent back andforth may not be regular all the time. This may be due to the soft timerissue, usage of a mobile device by a user, network delay, or the like.Particularly a user's use of the application can greatly alter thekeepalive activity, resulting in highly variable keepalive intervals.Similarly, another ambiguity in detecting keepalives can be theinformation size (byte size). The information size can be irregular dueto the design of the application or the server or other reasons. Forexample, an application may send different sized information but withinsome bound, e.g., 40-50 bytes for every keepalive spot. The keepalivedetection technology can detect and resolve any ambiguities in therecorded netlog data in the process of detecting keepalives. Thekeepalive detection technology can do so by detecting a regular intervaland regular byte sizes of data sent back and forth between the mobiledevice and the associated server. In the table 100A, the sendbytes 181and the recbytes 182 fields can be the regular byte sizes for keepalivesfrom applications. The table 100A can also include a field for theregular interval and/or results from any other intermediate calculations(e.g., standard deviation, quartiles, variance, etc.) performed in theprocess of determining the regular interval and/or regular byte sizes.

In some embodiments, the keepalive detection technology can detect apattern of data sent (i.e., data sent from an application to a server orfromapp bytes or sendbytes) and data received (i.e., data received bythe application from the server or fromnet bytes or recbytes) as aregular pattern if, for example, one or more of the following conditionsare true.

1. The pattern occurs more than $X times per $D duration. The $ sign isused herein to indicate that the frequency parameter “X” and theduration parameter “D” are tunable. In one example implementation, apattern of fromapp bytes and fromnet bytes occurring 10-15 times per daycan be considered a regular pattern.2. The interval time is uniform. The interval is uniform if 1^(st)quartile and 3^(rd) quartile's difference is smaller than $Y % of medianinterval. In one embodiment, 10-15% can be used for $Y %. Alternatively,in some implementations, without looking at 1^(st) or 3^(rd) quartiles,a pattern can be declared as uniform if it contains a sequence of $Kkeepalives (e.g., fromapp and fromnet bytes, fromapp bytes or fromnetbytes) whose intervals' variance is smaller than $V. In one exampleimplementation, $K=3 and $V=0.1 can be used. The $ sign is used hereinto indicate that the frequency parameter “Y,” “K” and “V” are tunable.3. The median interval time is bigger than $Z seconds. In one exampleimplementation, 60 seconds can be used for $Z. The $ sign is used hereinto indicate that the median interval time “Z” is tunable.

The parameters described above can generally be made tighter or looser(i.e., higher or lower) to adjust the aggressiveness in which thepattern is to be identified as a pattern having a regular interval. Insome embodiments, all three of the conditions described above may needto be satisfied in order to determine whether a pattern has a regularinterval or an irregular interval.

In some embodiments, the keepalive detection technology can detectregular byte size pattern of an application, by using the followingmethodology.

1. Check fromapp/fromnet bytes. If same fromapp/fromnet bytes occur inregular interval (e.g., as defined above), then the keepalive detectiontechnology detects a keepalive.2. If 1 fails, the keepalive detection technology can find the patternfrom the same fromapp bytes. If the pattern occurs in a regularinterval, then the keepalive detection technology detects a keepalive.3. If 2 fails, the keepalive detection technology can find the patternjust from the same fromnet bytes. If the patterns occurs in a regularinterval, then the keepalive detection technology detects a keepalive.4. If 3 fails, the keepalive detection technology can approximatelycluster fromapp/fromnet bytes. With a clustering algorithm (e.g.,K-means), the keepalive detection technology can identify similar sizedfromapp/fromnet bytes patterns. If the sizes in the cluster are similar(e.g., small variance $V2, another tunable parameter), and if they occurin a regular interval then the keepalive detection technology detects akeepalive. In some embodiments, the clustering technique in statisticalprogramming languages (e.g., R for Statistical Computing) can be used.Alternatively, a bucketing method can be employed to bucket thefromapp/fromnet bytes.5. If 4 fails, keepalive detection technology can apply a clusteringalgorithm only to fromapp bytes. If the biggest cluster's variance issmaller than $V2 and the fromapp bytes occur in a regular interval, thenthe keepalive detection technology detects a keepalive.6. If 5 fails, the keepalive detection technology can apply a clusteringalgorithm only to fromnet bytes. If the biggest cluster's variance issmaller than $V2 and they occur in a regular interval, then thekeepalive detection technology detects a keepalive.

The keepalive detection technology can then confirm successful detectionof a keepalive if (1) some of the keepalive entries share the same TCPsession or connection (e.g., based on the TCP session identifier) and if(2) the keepalives are proxy streamed. The determination of regularinterval and regular byte sizes of keepalives for detecting thekeepalives are described in detail with respect to the network log dataanalyzer component of a keepalive detector in FIGS. 3 and 4B and logicflow diagrams of FIGS. 5-8.

In some embodiments, the keepalive detection technology can analyzeinformation in a traffic data report (TDR) in detecting keepalives. ATDR or TDR message can be used to report traffic data immediately aftertheir completion (e.g., handshakes). The detection of a keepalive caninclude examining a TDR message including stream data (or data from aTCP stream) for socket time created and an amount of data transferred.For example, based on the socket time created, the keepalive detectiontechnology can determine if the time of creation of the socket was muchbefore the current time (i.e., T_(create)<<T_(now)). Similarly, based onthe amount of data transferred, the keepalive detection technology candetermine if some stream data transferred is less than a threshold(e.g., MAX_KEEP_ALIVE_PACKET). Based on these determinations, thekeepalive detection technology can detect whether the TDR messageincluding the stream data includes a keepalive. Once a stream has beenidentified to contain keepalives, any traffic on that stream can becategorized as keepalives in some embodiments.

In some embodiments, the accuracy in detecting keepalives by analyzingTDR messages can be improved based on an analysis of frequency of datatransferred. The frequency of data transferred can be determined basedon event history from the TDR messages by, for example, analyzinginterval for keepalives.

The keepalive detection technology includes a data structure for storinginformation about a connection object that is possibly a keepalive andany other data needed from the TDR messages. The data structure can alsocomprise a container (e.g., a class or data structure) for storing theconnection object. The container can be based on recurring requests (RR)(i.e., based on identifying similar requests from an application forpolling, caching, etc.) and can be mapped to a connection ID. Thekeepalive detection technology can, in some embodiments, reportkeepalive via an analysis field.

In some embodiments, the keepalive detection technology can implementkeepalive detection by creating a connections container. On TDRexecution (for keepalives, handling TDR_TYPE_STREAM_DATA), the keepalivedetection technology determines a connection ID which is a unique valueassociated with the TDR message including stream data. The keepalivedetection technology then searches for an appropriate connection in aconnections map using the connection ID. In the event that a connectionobject with a matching connection ID is found, the keepalive detectiontechnology updates the connection object and analytics (e.g., timingcalculations, amount of small data transfers). In some embodiments, whena connection object with a matching connection ID cannot be found, thekeepalive detection technology creates a connection object withinformation from the TDR message and inserts the connection object intothe connections map with the connection ID. Any changes associated withthe connection object is then reported in the analysis field of a log(e.g., a client reporting and capture service or CRCS log). On executionof a connection tear down (CTD) event or connection termination event(i.e., an event when a TCP connection is terminated by the applicationor the server), the keepalive detection technology searches for anappropriate connection in the connections map using the connection ID.In case a connection object with a matching connection ID is found, theconnection object is removed from the connection map and deleted.

As described above, the keepalive detection technology can implement adetection logic that in response to detecting a TDR message with typeTDR_TYPE_STREAM_DATA for a socket that was created more than, forexample, a minimum interval ago (e.g.,SC_MIN_TCPCONNECTION_CREATION_INTERVAL seconds ago, e.g., default 300seconds), creates a connection object. This connection object is apotential keepalive connection. For such a connection object, thedetection logic can create a weight variable (e.g., a “keepaliveweight”) which can be initialized on connection object creation withvalue=1. Analyzing each TDR message, the keepalive weight can beincreased by 1, for example, if the amount of data transferred from alocal proxy on a mobile device to a proxy server (e.g., on a hostserver) and from the server to the mobile device is less than, forexample, SC_MAX_BYTES_AMOUNT bytes (e.g., default 100 bytes) and timesince last data transfer is more than, for example, SC_MIN_IT seconds(e.g., default 300 seconds). When the keepalive weight is more than athreshold (e.g., SC_KEEPALIVE_WEIGHT, with a default value of e.g., 3),the keepalive detection technology can assume that a keepalive has beendetected.

The keepalive analysis and detection, including each change in theconnection object can be reported, for example, in an analysis field. Anexample data structure for reporting keepalives have the form of:

-   -   KA[KA1/KA2/KA3/KA4]

KA1 is a unique ID for connection or connection ID, KA2 is a connectioncreation time, KA3 is a flag indicating whether the connection isalready detected as a keepalive and can be a Boolean value (0/1) and KA4is the keepalive weight.

Once a TCP stream has been identified to contain keepalives, any trafficon that stream can be categorized as keepalives. This is because the KA3flag value reflects whether the connection has been identified ascontaining keepalives. In some embodiments, the KA3 flag does not tellwhether the reported packet in the TCP stream is believed to be akeepalive. In some embodiments, the keepalive detection technologyincludes an additional flag KA5 which can be used to indicate whetherthe packet contained in the TCP stream is a keepalive or not. Thus, insome embodiments, the data structure for reporting keepalives can be ofthe following example form:

-   -   KA[KA1/KA2/KA3/KA4/KA5]

KA1 is a unique ID for the connection, KA2 is the connection creationtime, KA3 is an indication whether the connection is already detected askeepalive and can be a value of 0 or 1, KA4 is the keepalive weight andKA5 is an indication whether the current packet is a keepalive and canhave a value of 0 or 1. An example of a portion of a netlog reportincluding the data structure for reporting keepalives is provided below:

2013-04-30 12:49:58.571 netlog 10 240 92 92 240 0 0rptuse20120814.getjar.com com.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/0/1/0] 1 12272013-04-30 12:56:59.916 netlog 10 0 2 2 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/0/2/1] 1 12272013-04-30 13:00:05.295 netlog 10 0 4 4 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/1/3/1] 1 12272013-04-30 13:06:11.904 netlog 10 0 4 4 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/1/4/1] 1 12272013-04-30 13:12:21.157 netlog 10 0 2 2 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/1/5/1] 1 12272013-04-30 13:15:25.986 netlog 10 0 4 4 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/1/6/1] 1 12272013-04-30 13:21:34.643 netlog 10 0 4 4 0 0 0 rptuse20120814.getjar.comcom.accuweather.androidbackground proxy_stream KA[138806279670/1367326198/1/7/1] 1 1227

As shown above, the first netlog record shows that KA5 flag to be 0indicating that the proxy_stream data did not carry the keepalive. Eachsuccessive netlog record shows that the KA4 is incremented by 1 and whenthe KA4 flag reaches an example default weight of 3, the KA3 flag isflipped from 0 to 1 indicating detection of a keepalive. The keepalivedetection based on analysis of TDR messages are described in detail withrespect to the connection analyzer of the keepalive detector 305 in FIG.3 and FIG. 9.

FIG. 1B depicts an example diagram of a system where a host serverfacilitates management of traffic, content caching, and/or resourceconservation between mobile devices (e.g., wireless devices), anapplication server or content provider, or other servers such as an adserver, promotional content server, an e-coupon server or a messagingserver (e.g., Google Cloud Messaging (GCM) server, the ExchangeActiveSync (EAS) server) in a wireless network (or broadband network)for resource conservation. The host server can further determineparameters that can be used in identifying keepalives from a TCP streamfor optimizing keepalive traffic in a mobile network.

The client devices 150 can be any system and/or device, and/or anycombination of devices/systems that is able to establish a connection,including wired, wireless, cellular connections with another device, abase station/cell provider 112, a server and/or other systems such ashost server 100 and/or application server/content provider 110. Clientdevices 150 will typically include a display and/or other outputfunctionalities to present information and data exchanged between amongthe devices 150 and/or the host server 100 and/or applicationserver/content provider 110. The application server/content provider 110can be any server including third party servers or service/contentproviders further including advertisement, promotional content,publication, or electronic coupon servers or services. Similarly,separate advertisement servers 120 a, promotional content servers 120 b,and/or e-Coupon servers 120 c as application servers or contentproviders are illustrated by way of example.

For example, the client/mobile devices 150 can include mobile, handheldor portable devices, wireless devices, or non-portable devices and canbe any of, but not limited to, a server desktop, a desktop computer, acomputer cluster, or portable devices, including a notebook, a laptopcomputer, a handheld computer, a palmtop computer, a mobile phone, acell phone, a smart phone, a PDA, a Blackberry device, a Palm device,any tablet, a phablet (a class of smart phones with larger screen sizesbetween a typical smart phone and a tablet), a handheld tablet (e.g., aniPad, the Galaxy series, the Nexus, the Kindles, Kindle Fires, anyAndroid-based tablets, Windows-based tablets, or any other tablet), anyportable readers/reading devices, a hand held console, a hand heldgaming device or console, a head mounted device, a head mounted display,a thin client or any SuperPhone such as the iPhone, and/or any otherportable, mobile, hand held devices, or fixed wireless interface such asa M2M device, etc. In one embodiment, the client devices 150 (or mobiledevices 150), host server 100, and application server 110 are coupledvia a network 106 and/or a network 108. In some embodiments, the devices150 and host server 100 may be directly connected to one another.

The input mechanism on client devices 150 can include touch screenkeypad (including single touch, multi-touch, gesture sensing in 2D or3D, etc.), a physical keypad, a mouse, a pointer, a track pad, a stylus,a stylus detector/sensor/receptor, motion detector/sensor (e.g.,including 1-axis, 2-axis, 3-axis accelerometer, etc.), a facedetector/recognizer, a retinal detector/scanner, a light sensor,capacitance sensor, resistance sensor, temperature sensor, proximitysensor, a piezoelectric device, device orientation detector (e.g.,electronic compass, tilt sensor, rotation sensor, gyroscope,accelerometer), or any combination of the above.

Signals received or detected indicating user activity at client devices150 through one or more of the above input mechanisms, or others, can beused in the disclosed technology in acquiring context awareness at theclient device 150. Context awareness at client devices 150 generallyincludes, by way of example but not limitation, client device 150operation or state acknowledgement, management, useractivity/behavior/interaction awareness, detection, sensing, tracking,trending, and/or application (e.g., mobile applications) type, behavior,activity, operating state, etc.

Context awareness in the present disclosure also includes knowledge anddetection of network side contextual data and can include networkinformation such as network capacity, bandwidth, traffic, type ofnetwork/connectivity, and/or any other operational state data. Networkside contextual data can be received from and/or queried from networkservice providers (e.g., cell provider 112 and/or Internet serviceproviders) of the network 106 and/or network 108 (e.g., by the hostserver and/or devices 150). In addition to application context awarenessas determined from the client 150 side, the application contextawareness may also be received from or obtained/queried from therespective application/service providers 110 (by the host 100 and/orclient devices 150).

The host server 100 can use, for example, contextual informationobtained for client devices 150, networks 106/108, applications (e.g.,mobile applications), application server/provider 110, or anycombination of the above, to manage the traffic in the system to satisfydata needs of the client devices 150 (e.g., to satisfy application orany other request including HTTP request). In one embodiment, thetraffic is managed by the host server 100 to satisfy data requests madein response to explicit or non-explicit user 103 requests (e.g., viauser interface 104) and/or device/application maintenance tasks. Thetraffic can be managed such that network consumption (e.g., use of thecellular network) is conserved for effective and efficient bandwidthutilization. In addition, the host server 100 can manage and coordinatesuch traffic in the system such that use of device 150 side resources(e.g., including but not limited to battery power consumption, radiouse, processor/memory use) are optimized with a general philosophy forresource conservation while still optimizing performance and userexperience. The host server 100 may also indirectly manage traffic viacreation, selection and/or deployment of traffic blocking policy forimplementation on the mobile device in some embodiments.

For example, in context of battery conservation, the device 150 canobserve user activity (for example, by observing user keystrokes,backlight status, or other signals via one or more input mechanisms,etc.) and alter device 150 behaviors. The device 150 can also requestthe host server 100 to alter the behavior for network resourceconsumption based on user activity or behavior.

In one embodiment, the traffic management for resource conservationand/or keepalive optimization/algorithms for signaling optimization isperformed using a distributed system between the host server 100 andclient device 150. The distributed system can include proxy server andcache components on the server side 100 and on the device/client side,for example, as shown by the server cache 135 on the server 100 side andthe local cache 185 on the client 150 side. In one embodiment, thetraffic management for reducing signaling in the network and reducing oralleviating network congestion can be implemented on the mobile device150 without any support from the server-side proxy or other network-sidecomponents.

Functions and techniques disclosed for context aware traffic managementand keepalive algorithms for resource conservation and reducing oroptimizing signaling in networks (e.g., network 106 and/or 108) anddevices 150, reside in a distributed proxy and cache system. The proxyand cache system can be distributed between, and reside on, a givenclient device 150 in part or in whole and/or host server 100 in part orin whole. The distributed proxy and cache system are illustrated withfurther reference to the example diagram shown in FIG. 1C. Functions andtechniques performed by the proxy and cache components in the clientdevice 150 and the related components therein are described,respectively, in detail with further reference to the examples of FIG.2A.

In one embodiment, client devices 150 communicate with the host server100 and/or the application server 110 over network 106, which can be acellular network and/or a broadband network. To facilitate overalltraffic management between devices 150 and various applicationservers/content providers 110 to implement network (bandwidthutilization) and device resource (e.g., battery consumption), the hostserver 100 can communicate with the application server/providers 110over the network 108, which can include the Internet (e.g., a broadbandnetwork).

In general, the networks 106 and/or 108, over which the client devices150, the host server 100, and/or application server 110 communicate, maybe a cellular network, a broadband network, a telephonic network, anopen network, such as the Internet, or a private network, such as anintranet and/or the extranet, or any combination thereof. For example,the Internet can provide file transfer, remote login, email, news, RSS,cloud-based services, instant messaging, visual voicemail, push mail,VoIP, and other services through any known or convenient protocol, suchas, but not limited to the TCP/IP protocol, UDP, HTTP, DNS, FTP, UPnP,NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The networks 106 and/or 108 include any collection of distinct networksoperating wholly or partially in conjunction to provide connectivity tothe client devices 150 and the host server 100 and may appear as one ormore networks to the serviced systems and devices. In one embodiment,communications to and from the client devices 150 can be achieved by anopen network, such as the Internet, or a private network or broadbandnetwork, such as an intranet and/or the extranet. In one embodiment,communications can be achieved by a secure communications protocol, suchas secure sockets layer (SSL) or transport layer security (TLS).

In addition, communications can be achieved via one or more networks,such as, but not limited to, one or more of WiMax, a Local Area Network(LAN), Wireless Local Area Network (WLAN), a Personal area network(PAN), a Campus area network (CAN), a Metropolitan area network (MAN), aWide area network (WAN), a Wireless wide area network (WWAN), or anybroadband network, and further enabled with technologies such as, by wayof example, Global System for Mobile Communications (GSM), PersonalCommunications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G,2.5G, 3G (e.g., WCDMA/UMTS-based 3G networks), 4G, IMT-Advanced, pre-4G,LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks,enhanced data rates for GSM evolution (EDGE), General packet radioservice (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, HSPA+,UMTS-TDD, 1×RTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS,extensible messaging and presence protocol (XMPP), real time messagingprotocol (RTMP), instant messaging and presence protocol (IMPP), instantmessaging, USSD, IRC, or any other wireless data networks, broadbandnetworks, or messaging protocols.

FIG. 1C depicts an example diagram of a proxy and cache systemdistributed between the host server and device which facilitates networktraffic management between a device, an application server or contentprovider, or other servers such as an ad server, promotional contentserver, an e-coupon server or a messaging server (e.g., Google CloudMessaging (GCM) server, the Exchange ActiveSync (EAS) server) forresource conservation and content caching. The proxy system distributedamong the host server and the device can further identify keepalivesfrom a TCP stream on the mobile device for optimizing keepalive trafficin a mobile network.

The distributed proxy and cache system can include, for example, theproxy server 125 (e.g., remote proxy) and the server cache 135components on the server side. The server-side proxy 125 and cache 135can, as illustrated, reside internal to the host server 100. Inaddition, the proxy server 125 and cache 135 on the server-side can bepartially or wholly external to the host server 100 and in communicationvia one or more of the networks 106 and 108. For example, the proxyserver 125 may be external to the host server and the server cache 135may be maintained at the host server 100. Alternatively, the proxyserver 125 may be within the host server 100 while the server cache 135is external to the host server 100. In addition, each of the proxyserver 125 and the server cache 135 may be partially internal to thehost server 100 and partially external to the host server 100. Theapplication server/content provider 110 can be any server includingthird-party servers or service/content providers further includingadvertisement, promotional content, publication, or electronic couponservers or services. Similarly, separate advertisement servers 120A,promotional content servers 120B, e-Coupon servers 120C, and/ormessaging servers (e.g., GCM, EAS servers) 120D as application serversor content providers are illustrated by way of example.

The distributed system can also include, in one embodiment, client-sidecomponents, including by way of example but not limitation, a localproxy 175 (e.g., a mobile client on a mobile device) and/or a localcache 185, which can, as illustrated, reside internal to the device 150(e.g., a mobile device).

In addition, the client-side proxy 175 and local cache 185 can bepartially or wholly external to the device 150 and in communication viaone or more of the networks 106 and 108. For example, the local proxy175 may be external to the device 150 and the local cache 185 may bemaintained at the device 150. Alternatively, the local proxy 175 may bewithin the device 150 while the local cache 185 is external to thedevice 150. In addition, each of the proxy 175 and the cache 185 may bepartially internal to the host server 100 and partially external to thehost server 100.

In one embodiment, the distributed system can include an optionalcaching proxy server 199. The caching proxy server 199 can be acomponent which is operated by the application server/content provider110, the host server 100, or a network service provider (e.g., 112), andor any combination of the above to facilitate network traffic managementfor network and device resource conservation. Proxy server 199 can beused, for example, for caching content to be provided to the device 150,for example, from one or more of, the application server/provider 110,host server 100, and/or a network service provider. Content caching canalso be entirely or partially performed by the remote proxy 125 tosatisfy application requests or other data requests at the device 150.

In context-aware traffic management and optimization for resourceconservation and/or keepalive optimization in signaling optimization ina network (e.g., cellular or other wireless networks), characteristicsof user activity/behavior and/or application behavior at a mobile device(e.g., any wireless device) 150 can be tracked by the local proxy 175and communicated over the network 106 to the proxy server 125 componentin the host server 100, for example, as connection metadata. The proxyserver 125, which in turn is coupled to the application server/provider110, provides content and data to satisfy requests made at the device150. The local proxy 175 can be a protocol-agnostic component that canidentify keepalives from the TCP stream, regardless of the applicationlayer protocol.

In addition, the local proxy 175 can identify and retrieve mobile deviceproperties, including one or more of battery level, network that thedevice is registered on, radio state, signal strength, cell identifier(i.e., cell ID), location area code, or whether the mobile device isbeing used (e.g., interacted with by a user). In some instances, thelocal proxy 175 can delay, expedite (prefetch), and/or modify data priorto transmission to the proxy server 125, when appropriate, as will befurther detailed with references to the description associated with theexamples of FIG. 2A.

The local cache 185 can be included in the local proxy 175 or coupled tothe local proxy 175 and can be queried for a locally stored response tothe data request prior to the data request being forwarded on to theproxy server 125. Locally cached responses can be used by the localproxy 175 to satisfy certain application requests of the mobile device150, by retrieving cached content stored in the cache storage 185, whenthe cached content is still valid.

Similarly, the proxy server 125 of the host server 100 can also delay,expedite, or modify data from the local proxy prior to transmission tothe content sources (e.g., the application server/content provider 110).In addition, the proxy server 125 uses device properties and connectionmetadata to generate rules for satisfying request of applications on themobile device 150. The proxy server 125 can gather real time trafficinformation about requests of applications for later use in optimizingsimilar connections with the mobile device 150 or other mobile devices.The proxy server 125 can also receive or aggregate network communicationdata logs and perform statistical analyses on data sent and received todetermine regular intervals and regular byte sizes for keepalives fromvarious applications. The proxy server 125 can further push suchinformation to multiple mobile devices to equip the mobile devices forkeepalive detection and subsequent keepalive optimization.

In general, the local proxy 175 and the proxy server 125 are transparentto the multiple applications executing on the mobile device. The localproxy 175 is generally transparent to the operating system or platformof the mobile device and may or may not be specific to devicemanufacturers. In some instances, the local proxy 175 is optionallycustomizable in part or in whole to be device specific. In someembodiments, the local proxy 175 may be bundled into a wireless model, afirewall, and/or a router.

In one embodiment, the host server 100 can in some instances, utilizethe store and forward functions of a short message service center (SMSC)162, such as that provided by the network service provider, incommunicating with the device 150 in achieving network trafficmanagement. Note that SMSC 162 can also utilize any other type ofalternative channel including USSD or other network control mechanisms.The host server 100 can forward content or HTTP responses to the SMSC162 such that it is automatically forwarded to the device 150 ifavailable and for subsequent forwarding if the device 150 is notcurrently available.

In general, the disclosed distributed proxy and cache system enablesidentification of keepalives from the TCP stream for keepaliveoptimization. The disclosed distributed proxy and cache system furtherenables optimization of network usage, for example, by serving requestsfrom the local cache 185, the local proxy 175 reduces the number ofrequests that need to be satisfied over the network 106. Further, thelocal proxy 175 and the proxy server 125 may filter irrelevant data fromthe communicated data. In addition, the local proxy 175 and the proxyserver 125 can also accumulate low priority data and send it in batchesto avoid the protocol overhead of sending individual data fragments. Thelocal proxy 175 and the proxy server 125 can also compress or transcodethe traffic, reducing the amount of data sent over the network 106and/or 108. The signaling traffic in the network 106 and/or 108 can bereduced, as the networks are now used less often and the network trafficcan be synchronized among individual applications.

With respect to the battery life of the mobile device 150, by servingapplication or content requests from the local cache 185, the localproxy 175 can reduce the number of times the radio module is powered up.The local proxy 175 and the proxy server 125 can work in conjunction toaccumulate low priority data and send it in batches to reduce the numberof times and/or amount of time when the radio is powered up. The localproxy 175 can synchronize the network use by performing the batched datatransfer for all connections simultaneously. Furthermore, by preventingthe mobile device from constantly attempting to signal the network thatis congested, and/or allowing selective (e.g., high priority) traffictowards the network, the local proxy 175 can conserve battery resourcesof the mobile device.

FIG. 1D illustrates an example diagram of the logical architecture of adistributed proxy and cache system. The distributed system can include,for example the following components:

Client Side Proxy 175: a component installed in a smartphone, mobiledevice or wireless device 150 that interfaces with device's operatingsystem, as well as with data services and applications installed in thedevice. The client side proxy 175 is typically compliant with and ableto operate with standard or state of the art networking protocols.Additional components and features of the client-side proxy 175 areillustrated with further references to the examples of FIG. 2A.

The server side proxy 125 can include one or more servers that caninterface with third-party application servers (e.g., 199), mobileoperator's network (which can be proxy 199 or an additional server thatis not illustrated) and/or the client side proxy 175. In general, theserver side proxy 125 can be compliant with and is generally able tooperate with standard or state of the art networking protocols and/orspecifications for interacting with mobile network elements and/orthird-party servers. In one embodiment, the server-side proxy 125 canutilize the store and forward functions of a short message servicecenter (SMSC) 162 in communicating with the client-side proxy 175 on themobile device 150 to optimize network traffic.

Log Storage and Processing Service (LSPS) 174: The log storage andprocessing service, server, system or component 174 can providereporting and usage analytics services. The LSPS 174 can collectinformation (e.g., logs) from the client side 175 and/or the server side125 and provide the necessary tools for producing reports and usageanalytics that can be used for analyzing traffic and signaling data. Theclient logs (e.g., logs on the client device 150 aggregated by the localproxy 175) are stored in the device until a data channel is activated,and they are then transferred in binary format to the LSPS 174. In oneembodiment, the logs are processed using log processing tools providedby the LSPS 174. The processed logs are subsequently stored in adistributed database. The logs may be used for reporting as well as fortroubleshooting issues. For example, analytics from the logs can be usedby the proxy system in managing, reducing or optimizing network trafficor by the network operator in monitoring their networks for possibleimprovements and enhancements. Note that LSPS 174 as illustrated may bea server separate from the server-side proxy 125, or it may be acomponent of the server-side proxy 125, residing partially or whollytherein.

In one implementation, the level of logging (e.g., types of data to belogged, and the like) can be specified using configuration settings inthe client-side proxy 175 and/or the server-side proxy 125. Various datarelating to bytes and transactions, network connectivity, power,subscriber count, and the like may be logged, and/or processed usingdefault (or other) settings on a periodic (e.g., hourly, daily, and thelike) basis.

Bytes and Transactions data may include a number of bytes transacted(both to and from), the total number of transactions between theclient-side proxy 175 and each application, the client-side proxy 175and the network (e.g., radio access network 112), the client-side proxy175 and its cache, and the like. Network Connectivity data may include,for example, total time the device spends in “data connected” state(based on a two-state connectivity model), total number of transitionsinto the data connected state, the number of times the radio transitionsinto the data connected state due to a network request that was proxiedthrough the client-side proxy 175, total time spent in the dataconnected state due to a network request that was proxied through theclient-side proxy 175, the number of transitions into data connectedmode saved by the client-side and/or server-side proxy system, theamount of time in data connected state saved by the client-side and/orserver-side proxy system, simulated values for the previous four items,as if traffic proxied via client-side and/or server-side proxy systemwere the only traffic on the device. Network connectivity data can alsoinclude the amount of time taken to transition from an idle state toconnected state (i.e., setup time), a baseline or a reference determinedfrom a sample of setup times, and the like. Power-related data mayinclude, for example, each one-percent (or any other percentage value)change in the battery level, the total time the device is powered on butnot connected to a power source, and the like. Subscriber count data mayinclude, for example, the number of new subscribers observed in a periodand the number of active subscribers in the period. This data may beaggregated by the host server, for example. Reporting of the above datacan be done based on variables such as network bearer type (e.g., all,mobile or Wi-Fi), category (e.g., all, device model or applicationname), time (e.g., hour, day or month), and the like, or combinationsthereof.

FIG. 1E illustrates an example diagram showing the architecture ofclient-side components in a distributed proxy and cache system having akeepalive optimizer for optimizing keepalive and other backgroundtraffic in a wireless network.

The client-side proxy 175 components can include software components oragents installed on the mobile device that enable traffic optimizationand perform the related functionalities on the client side. Mobile OSand Apps 165 include components of the client side proxy 175 can operatetransparently for end users and applications 163, and interface with thedevice's operating system (OS) 162. The client side proxy 175 can beinstalled on mobile devices for optimization to take place, and it caneffectuate changes on the data routes and/or timing. Once data routingis modified, the client side proxy 175 can respond to applicationrequests to service providers or host servers, in addition to or insteadof letting those applications 163 access data network directly. Ingeneral, applications 163 on the mobile device will not notice that theclient side proxy 175 is responding to their requests.

Some example components of the client side proxy 175 are described asfollows:

Device State Monitor 121: The device state monitor 121 can beresponsible for identifying several states and metrics in the device,such as network status (e.g., radio on/off status, connected to Wi-Fi,2G, 3G or other mobile network), display status, battery level (e.g.,via the radio/battery information 161), transparent mode status, etc.,such that the remaining components in the client side proxy 175 canoperate and make decisions according to device state, acting in anoptimal way in each state.

Traffic Recognizer 122: The traffic recognizer 122 analyzes all trafficbetween the wireless device applications 163 and their respective hostservers in order to identify recurrent patterns. Supported transportprotocols include, for example, DNS, HTTP and HTTPS, such that trafficthrough those ports is directed to the client side proxy 175. Whileanalyzing traffic, the client side proxy 175 can identify recurringpolling patterns which can be candidates to be performed remotely by theserver side proxy 125, and send to the protocol optimizer 123.

Protocol Optimizer 123: The protocol optimizer 123 can implement thelogic of serving recurrent requests from the local cache 185 instead ofallowing those request go over the network to the serviceprovider/application host server. One of its tasks is to eliminate orminimize the need to send requests to the network, positively affectingnetwork congestion and device battery life.

Local Cache 185: The local cache 185 can store responses to recurrentrequests, and can be used by the Protocol Optimizer 123 to sendresponses to the applications 163.

Traffic Scheduler 124: The traffic scheduler 124 can temporally movecommunications to optimize usage of device resources by unifyingkeepalive signaling so that some or all of the different applications163 can send keepalive messages at the same time (traffic pipelining).Traffic scheduler 124 may also decide to delay transmission of data thatis not relevant at a given time (for example, when the device is notactively used).

The keepalive detector 305: The keepalive detector 305 can detectkeepalives based on various methodologies from the TCP stream to enablekeepalive optimization, which can conserve resources on the mobiledevice and the network. In some embodiments, the keepalive detector 305implementing the keepalive detection technology enables keepalives fromapplications to be detected in real-time, based on information relatedto the interval between data sent/received, size of the datasent/received, whether the data sent/received are associated with thesame connection identifier, or the like. Various aspects of thekeepalive detector 305 are described in detail with respect to FIG. 3.

The keepalive optimizer 300: Once the keepalives are detected by thekeepalive detector, the keepalive optimizer 300 can optimize keepaliveand other non-user interactive or background traffic using variousmethodologies. In one embodiment, the keepalive optimizer 300 canimprove the efficiency of keepalive transactions and manage long-livedconnections between mobile applications and associated application/hostservers. For example, the keepalive optimizer 300 can manage long-livedconnections with fewer keepalives, utilize radio-awareness, applicationbehavior and/or device state to schedule transmission of keepalives andother background traffic, and the like. By performing theseoptimizations, the keepalive optimizer 300 can reduce unnecessarytraffic in the mobile network, reduce battery resource consumption onmobile devices, save on bandwidth resource consumption and managelong-lived connections among others. Various aspects of keepaliveoptimization techniques of the keepalive optimizer 300 are described indetail in a related U.S. Provisional Patent Application Ser. No.61/833,838 titled “KEEPALIVE ALGORITHMS FOR SIGNALING OPTIMIZATION IN AWIRELESS NETWORK FOR TRAFFIC UTILIZING PROPRIETARY AND NON-PROPRIETARYPROTOCOLS” filed on Jun. 11, 2013 (Attorney Docket No. 076443-8170.US00)and U.S. Provisional Patent Application Ser. No. 61/836,095 titled“ENGINEERING DELAY IN SENDING BACKGROUND REQUESTS FOR SIGNALINGOPTIMIZATION IN A WIRELESS NETWORK FOR TRAFFIC UTILIZING PROPRIETARY ANDNON-PROPRIETARY PROTOCOLS” filed on Jun. 17, 2013 (Attorney Docket No.076443-8173.US01), the entire content of which are incorporated byreference herein.

Policy Manager 129: The policy manager 129 can store and enforce trafficoptimization and reporting policies provisioned by a Policy ManagementServer (PMS). At the client side proxy 175 first start, trafficoptimization and reporting policies (policy profiles) that are to beenforced in a particular device can be provisioned by the PolicyManagement Server. Enforcing traffic management policies at the device'sIP layer lets an operator manage traffic before it uses radio accessednetwork resources. Policy usage can range from creating highly targetedsubscriber plans to proactively and/or reactively managing networkcongestion. In one implementation, the conditions for selecting a policyfor enforcement, and/or conditions for dropping an implemented policy,may be managed or coordinated by the policy manager 129. For example, insome embodiments, the policy manager 129 can manage and implementkeepalive and other background traffic optimization policies such asblocking policies, delaying policies, transmission policies, and/or thelike configured and provisioned by the PMS. For example, the PMS canhave two policy configurations for optimizing background requests: (1)true to enable the optimization and false to disable the optimizationand (2) length of delay cycle to be applied if there is no other eventtriggering undelay. Similarly, the PMS can provide and the policymanager 129 can implement other configurations for various components ofthe keepalive optimizer 300. In one embodiment, the policy manager 129can receive and implement a policy configuration from the PMS to enableor disable the keepalive optimizer 300 and/or the keepalive detector 305at an application level or at a user or device level. In someembodiments, the policy manager 129 can also receive and manageconfiguration parameters or settings for detecting keepalives by thekeepalive detector 305.

Watch Dog 127: The watch dog 127 can monitor the client side proxy 175operating availability. In case the client side proxy 175 is not workingdue to a failure or because it has been disabled, the watchdog 127 canreset DNS routing rules information and can restore original DNSsettings for the device to continue working until the client side proxy175 service is restored.

Reporting Agent 126: The reporting agent 126 can gather information(e.g., logs) about the events taking place in the device and send theinformation to the log storage and processing service 174, whichcollects and stores client-side and/or server-side proxy system logs.Event details are stored temporarily in the device and transferred tolog storage and processing service 174 only when the data channel stateis active. If the client side proxy 175 does not send records within aperiod of time (e.g., twenty-four hours), the reporting agent 126 may,in one embodiment, attempt to open the connection and send recordedentries or, in case there are no entries in storage, an empty reportingpacket. All reporting settings may be configured in the policymanagement server (PMS). The information in the logs may be used forreporting and/or troubleshooting, for example.

Push Client 128: The push client 128 can be responsible for the trafficbetween the server side proxy 125 and the client side proxy 175. Thepush client 128 can send out service requests like content updaterequests and policy update requests, and can receive updates to thoserequests from the server side proxy 125. In addition, push client 128can send data to a log storage and processing service 174, which may beinternal to or external to the server side proxy 125.

The proxy server 199 has a wide variety of uses, from speeding up a webserver by caching repeated requests, to caching web, DNS and othernetwork lookups for a group of clients sharing network resources. Theproxy server 199 is optional. The distributed proxy and cache system(125 and/or 175) allows for a flexible proxy configuration using eitherthe proxy 199, additional proxy(s) in operator's network, or integratingboth proxies 199 and an operator's or other third-party's proxy.

FIG. 2A depicts a block diagram illustrating another example ofclient-side components in a distributed proxy and cache system, furtherincluding a keepalive detector that can identify keepalives from a TCPstream. The client-side components in a distributed proxy and cachesystem can reside on a mobile device (e.g., wireless device) 250 thatmanages traffic in a wireless network (or broadband network) forkeepalive detection, keepalive optimization, signaling optimization,resource conservation, content caching, and/or traffic management.

FIG. 2B depicts a block diagram illustrating additional components inthe local proxy shown in the example of FIG. 2A which is further capableof performing mobile traffic categorization and management based onapplication behavior and/or user activity.

The mobile device 250, which can be a device that is portable or mobile(e.g., any wireless device, e.g., mobile device 150 from FIG. 1B-1E),such as a portable phone, generally includes, for example, a networkinterface 208, an operating system 204, a context API 206, and mobileapplications which may be proxy-unaware 210 or proxy-aware 220. Notethat while the client device 250 is specifically illustrated in theexample of FIG. 2A as a mobile device, such depiction is not alimitation, and mobile device 250 may be any wireless, broadband,portable/mobile or non-portable device able to receive and/or transmitsignals to satisfy data requests over a network including wired orwireless networks (e.g., Wi-Fi, cellular, Bluetooth, LAN, WAN, and thelike).

The network interface 208 can be a networking module that enables thedevice 250 to mediate data in a network with an entity that is externalto the mobile device 250, through any known and/or convenientcommunications protocol supported by the mobile device and the externalentity. The network interface 208 can include one or more of a networkadaptor card, a wireless network interface card (e.g., SMS interface,Wi-Fi interface, interfaces for various generations of mobilecommunication standards including but not limited to 2G, 3G, 3.5G, 4G,LTE, etc.), Bluetooth, or whether or not the connection is via a router,an access point, a wireless router, a switch, a multilayer switch, aprotocol converter, a gateway, a bridge, a bridge router, a hub, adigital media receiver, and/or a repeater.

Device 250 can further include, client-side components of thedistributed proxy and cache system which can include, a local proxy 275(e.g., a mobile client of a mobile device) and a cache 285. In oneembodiment, the local proxy 275 includes a user activity module 215, aproxy API 225, a request/transaction manager 235, a caching policymanager 245 having an application protocol module 248, a traffic shapingengine 255, and/or a connection manager 265. The traffic shaping engine255 may further include an alignment module 256 and/or a batching module257, the connection manager 265 may further include a radio controller266, a heartbeat manager 267, a keepalive detector 305 and a keepaliveoptimizer 300. The request/transaction manager 235 can further includean application behavior detector 236 having a prioritization engine 241,a pattern detector 237, an application profile generator 239, a timecriticality detection engine 242, an application state categorizer 243and an application traffic categorizer 244. In one embodiment, the localproxy or the device can further include a proprietary/non-standardprotocol adaptation engine 270 for optimizing traffic in a protocolagnostic manner.

Additional or less components/modules/engines can be included in thelocal proxy 275 and each illustrated component.

As used herein, a “module,” “manager,” “handler,” “detector,”“optimizer,” “interface,” “controller,” “normalizer,” “generator,”“invalidator,” or “engine” includes a general purpose, dedicated orshared processor and, typically, firmware or software modules that areexecuted by the processor. Depending upon implementation-specific orother considerations, the module, manager, handler, detector, optimizer,interface, controller, normalizer, generator, invalidator, or engine canbe centralized or its functionality distributed. The module, manager,handler, detector, optimizer, interface, controller, normalizer,generator, invalidator, or engine can include general or special purposehardware, firmware, or software embodied in a computer-readable(storage) medium for execution by the processor.

As used herein, a computer-readable medium or computer-readable storagemedium is intended to include all mediums that are statutory (e.g., inthe United States, under 35 U.S.C. 101), and to specifically exclude allmediums that are non-statutory in nature to the extent that theexclusion is necessary for a claim that includes the computer-readable(storage) medium to be valid. Known statutory computer-readable mediumsinclude hardware (e.g., registers, random access memory (RAM),non-volatile (NV) storage, to name a few), but may or may not be limitedto hardware.

In one embodiment, a portion of the distributed proxy and cache systemfor mobile traffic management resides in or is in communication with themobile device 250, including local proxy 275 (mobile client) and/orcache 285. The local proxy 275 can provide an interface on the mobiledevice 250 for users to access device applications and servicesincluding email, IM, voice mail, visual voicemail, feeds, Internet,games, productivity tools, or other applications, etc.

The local proxy 275 is generally application independent and can be usedby applications (e.g., both proxy-aware and proxy-unaware applications210 and 220 and other mobile applications) to open TCP (TransportControl Protocol) or other protocol based connections to a remote server(e.g., the server 100 in the examples of FIG. 1B-1C and/or server proxy125 shown in the examples of FIG. 1B). In some instances, the localproxy 275 includes a proxy API 225 which can be optionally used tointerface with proxy-aware applications 220 (or applications (e.g.,mobile applications) on a mobile device (e.g., any wireless device)).

The applications 210 and 220 can generally include any user application,widgets, software, HTTP-based application, web browsers, video or othermultimedia streaming or downloading application, video games, socialnetwork applications, email clients, RSS management applications,application stores, document management applications, productivityenhancement applications, and the like. The applications can be providedwith the device OS, by the device manufacturer, by the network serviceprovider, downloaded by the user, or provided by others.

One embodiment of the local proxy 275 includes or is coupled to acontext API 206, as shown. The context API 206 may be a part of theoperating system 204 or device platform or independent of the operatingsystem 204, as illustrated. The operating system 204 can include anyoperating system including but not limited to, any previous, current,and/or future versions/releases of, Windows Mobile, iOS, Android,Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.

The context API 206 may be a plug-in to the operating system 204 or aparticular client/application on the device 250. The context API 206 candetect signals indicative of user or device activity, for example,sensing motion, gesture, device location, changes in device location,device backlight, keystrokes, clicks, activated touch screen, mouseclick or detection of other pointer devices. The context API 206 can becoupled to input devices or sensors on the device 250 to identify thesesignals. Such signals can generally include input received in responseto explicit user input at an input device/mechanism at the device 250and/or collected from ambient signals/contextual cues detected at or inthe vicinity of the device 250 (e.g., light, motion, piezoelectric,etc.).

In one embodiment, the user activity module 215 interacts with thecontext API 206 to identify, determine, infer, detect, compute, predict,and/or anticipate, characteristics of user activity on the device 250.Various inputs collected by the context API 206 can be aggregated by theuser activity module 215 to generate a profile for characteristics ofuser activity. Such a profile can be generated by the user activitymodule 215 with various temporal characteristics. For instance, useractivity profile can be generated in real-time for a given instant toprovide a view of what the user is doing or not doing at a given time(e.g., defined by a time window, in the last minute, in the last 30seconds, etc.), a user activity profile can also be generated for a‘session’ defined by an application or web page that describes thecharacteristics of user behavior with respect to a specific task theyare engaged in on the mobile device 250, or for a specific time period(e.g., for the last 2 hours, for the last 5 hours).

Additionally, characteristic profiles can be generated by the useractivity module 215 to depict a historical trend for user activity andbehavior (e.g., 1 week, 1 mo., 2 mo., etc.). Such historical profilescan also be used to deduce trends of user behavior, for example, accessfrequency at different times of day, trends for certain days of the week(weekends or week days), user activity trends based on location data(e.g., IP address, GPS, or cell tower coordinate data) or changes inlocation data (e.g., user activity based on user location, or useractivity based on whether the user is on the go, or traveling outside ahome region, etc.) to obtain user activity characteristics.

In one embodiment, user activity module 215 can detect and track useractivity with respect to applications, documents, files, windows, icons,and folders on the device 250. For example, the user activity module 215can detect when an application or window (e.g., a web browser or anyother type of application) has been exited, closed, minimized,maximized, opened, moved into the foreground or into the background,multimedia content playback, etc.

In one embodiment, characteristics of the user activity on the device250 can be used to locally adjust behavior of the device (e.g., mobiledevice or any wireless device) to optimize its resource consumption suchas battery/power consumption and more generally, consumption of otherdevice resources including memory, storage, and processing power, and/orfurther optimize signaling in the network. In one embodiment, the use ofa radio on a device can be adjusted based on characteristics of userbehavior (e.g., by the radio controller 266 of the connection manager265) coupled to the user activity module 215. For example, the radiocontroller 266 can turn the radio on or off, based on characteristics ofthe user activity on the device 250. In addition, the radio controller266 can adjust the power mode of the radio (e.g., to be in a higherpower mode or lower power mode) depending on characteristics of useractivity.

In one embodiment, characteristics of the user activity on device 250can also be used to cause another device (e.g., other computers, amobile device, a wireless device, or a non-portable device) or server(e.g., host server 100 in the examples of FIG. 1B-1C) which cancommunicate (e.g., via a cellular or other network) with the device 250to modify its communication frequency with the device 250. The localproxy 275 can use the characteristics information of user behaviordetermined by the user activity module 215 to instruct the remote deviceas to how to modulate its communication frequency (e.g., decreasingcommunication frequency, such as data push frequency if the user isidle, requesting that the remote device notify the device 250 if newdata, changed, data, or data of a certain level of importance becomesavailable, etc.).

In one embodiment, the user activity module 215 can, in response todetermining that user activity characteristics indicate that a user isactive after a period of inactivity, request that a remote device (e.g.,server host server 100 or the network-side proxy 125 in the examples ofFIG. 1B-1C) send the data that was buffered as a result of thepreviously decreased communication frequency.

In addition, or in alternative, the local proxy 275 can communicate thecharacteristics of user activity at the device 250 to the remote device(e.g., host server 100 or the network-side proxy 125 in the examples ofFIG. 1B-1C) and the remote device determines how to alter its owncommunication frequency with the device 250 for network resourceconservation and conservation of resources of the mobile device 250.

One embodiment of the local proxy 275 further includes arequest/transaction manager 235, which can detect, identify, intercept,process and manage data requests initiated on the device 250, forexample, by applications 210 and/or 220, and/or directly/indirectly by auser request. The request/transaction manager 235 can determine how andwhen to process a given request or transaction, or a set ofrequests/transactions, based on transaction characteristics.

The request/transaction manager 235 can prioritize requests ortransactions made by applications and/or users at the device 250, forexample by the prioritization engine 241. Importance or priority ofrequests/transactions can be determined by the request/transactionmanager 235 by applying a rule set, for example, according to timesensitivity of the transaction, time sensitivity of the content in thetransaction, time criticality of the transaction, time criticality ofthe data transmitted in the transaction, and/or time criticality orimportance of an application making the request.

In addition, transaction characteristics can also depend on whether thetransaction was a result of user-interaction or other user-initiatedaction on the device (e.g., user interaction with an application (e.g.,a mobile application)). In general, a time critical transaction caninclude a transaction resulting from a user-initiated data transfer, andcan be prioritized as such. Transaction characteristics can also dependon the amount of data that will be transferred or is anticipated to betransferred as a result of the requested transaction. For example, theconnection manager 265 can adjust the radio mode (e.g., high power orlow power mode via the radio controller 266) based on the amount of datathat will need to be transferred.

In addition, the radio controller 266/connection manager 265 can adjustthe radio power mode (high or low) based on time criticality/sensitivityof the transaction. The radio controller 266 can trigger the use of highpower radio mode when a time-critical transaction (e.g., a transactionresulting from a user-initiated data transfer, an application running inthe foreground, any other event meeting a certain criteria) is initiatedor detected.

In general, the priorities can be set by default, for example, based ondevice platform, device manufacturer, operating system, etc. Prioritiescan alternatively or additionally be set by the particular application;for example, the Facebook application (e.g., a mobile application) canset its own priorities for various transactions (e.g., a status updatecan be of higher priority than an add friend request or a poke request;a message send request can be of higher priority than a message deleterequest), or an email client or IM chat client may have its ownconfigurations for priority. The prioritization engine 241 may includeset of rules for assigning priority.

The prioritization engine 241 can also track network providerlimitations or specifications on application or transaction priority indetermining an overall priority status for a request/transaction.Furthermore, priority can in part or in whole be determined by userpreferences, either explicit or implicit. A user can in general setpriorities at different tiers, such as, specific priorities forsessions, or types, or applications (e.g., comparing a browsing session,a gaming session, and an IM chat session, the user may set a gamingsession to always have higher priority than an IM chat session, whichmay have higher priority than web-browsing session). A user can setapplication-specific priorities, (e.g., a user may set Facebook-relatedtransactions to have a higher priority than LinkedIn-relatedtransactions), for specific transaction types (e.g., for all sendmessage requests across all applications to have higher priority thanmessage delete requests, for all calendar-related events to have a highpriority, etc.), and/or for specific folders.

The prioritization engine 241 can track and resolve conflicts inpriorities set by different entities. For example, manual settingsspecified by the user may take precedence over device OS settings,network provider parameters/limitations (e.g., set in default for anetwork service area, geographic locale, set for a specific time of day,or set based on service/fee type) may limit any user-specified settingsand/or application-set priorities. In some instances, a manualsynchronization request received from a user can override some, most, orall priority settings in that the requested synchronization is performedwhen requested, regardless of the individually assigned priority or anoverall priority ranking for the requested action.

Priority can be specified and tracked internally in any known and/orconvenient manner, including but not limited to, a binaryrepresentation, a multi-valued representation, a graded representationand all are considered to be within the scope of the disclosedtechnology.

TABLE 1 Change Change (initiated on device) Priority (initiated onserver) Priority Send email High Receive email High Delete email LowEdit email Often not (Un)read email Low possible to sync (Low ifpossible) Move message Low New email in Low deleted items Read more HighDownload High Delete an email Low attachment (Un)Read an email Low NewCalendar event High Move messages Low Edit/change Calendar High Anycalendar change High event Any contact change High Add a contact HighWipe/lock device High Edit a contact High Settings change High Searchcontacts High Any folder change High Change a setting High Connectorrestart High (if no Manual send/receive High changes nothing is sent) IMstatus change Medium Social Network Status Medium Updates Auction outbidor High Severe Weather Alerts High change notification Weather UpdatesLow News Updates Low

Table 1 above shows, for illustration purposes, some examples oftransactions with examples of assigned priorities in a binaryrepresentation scheme. Additional assignments are possible foradditional types of events, requests, transactions, and as previouslydescribed, priority assignments can be made at more or less granularlevels, e.g., at the session level or at the application level, etc.

As shown by way of example in the above table, in general, lowerpriority requests/transactions can include updating message status asbeing read, unread, deleting of messages, deletion of contacts; higherpriority requests/transactions can, in some instances include, statusupdates, new IM chat message, new email, calendar eventupdate/cancellation/deletion, an event in a mobile gaming session, orother entertainment related events, a purchase confirmation through aweb purchase or online, request to load additional or download content,contact book related events, a transaction to change a device setting,location-aware or location-based events/transactions, or any otherevents/request/transactions initiated by a user or where the user isknown to be, expected to be, or suspected to be waiting for a response,etc.

Inbox pruning events (e.g., email, or any other types of messages) aregenerally considered low priority and, absent other impending events,generally will not trigger use of the radio on the device 250.Specifically, pruning events to remove old email or other content can be‘piggy backed’ with other communications if the radio is not otherwiseon, at the time of a scheduled pruning event. For example, if the userhas preferences set to ‘keep messages for 7 days old,’ then instead ofpowering on the device radio to initiate deletion of the message fromthe device 250 the moment that the message has exceeded 7 days old, themessage is deleted when the radio is powered on next. If the radio isalready on, then pruning may occur as regularly scheduled.

The request/transaction manager 235 can use the priorities for requests(e.g., by the prioritization engine 241) to manage outgoing traffic fromthe device 250 for resource optimization (e.g., to utilize the deviceradio more efficiently for battery conservation). For example,transactions/requests below a certain priority ranking may not triggeruse of the radio on the device 250 if the radio is not already switchedon, as controlled by the connection manager 265. In contrast, the radiocontroller 266 can turn on the radio such that a request can be sentwhen a request for a transaction is detected to be over a certainpriority level.

In one embodiment, priority assignments (such as that determined by thelocal proxy 275 or another device/entity) can be used to cause a remotedevice to modify its communication with the frequency with the mobiledevice or wireless device. For example, the remote device can beconfigured to send notifications to the device 250 when data of higherimportance is available to be sent to the mobile device or wirelessdevice.

In one embodiment, transaction priority can be used in conjunction withcharacteristics of user activity in shaping or managing traffic, forexample, by the traffic shaping engine 255. For example, the trafficshaping engine 255 can, in response to detecting that a user is dormantor inactive, wait to send low priority transactions from the device 250,for a period of time. In addition, the traffic shaping engine 255 canallow multiple low priority transactions to accumulate for batchtransferring from the device 250 (e.g., via the batching module 257). Inone embodiment, the priorities can be set, configured, or readjusted bya user. For example, content depicted in Table 3 in the same or similarform can be accessible in a user interface on the device 250 and forexample, used by the user to adjust or view the priorities.

The batching module 257 can initiate batch transfer based on certaincriteria. For example, batch transfer (e.g., of multiple occurrences ofevents, some of which occurred at different instances in time) may occurafter a certain number of low priority events have been detected, orafter an amount of time elapsed after the first of the low priorityevent was initiated. In addition, the batching module 257 can initiatebatch transfer of the accumulated low priority events when a higherpriority event is initiated or detected at the device 250. Batchtransfer can otherwise be initiated when radio use is triggered foranother reason (e.g., to receive data from a remote device such as hostserver 100, server-side proxy 125). In one embodiment, an impendingpruning event (pruning of an inbox), or any other low priority events,can be executed when a batch transfer occurs.

In general, the batching capability can be disabled or enabled at theevent/transaction level, application level, or session level, based onany one or combination of the following: user configuration, devicelimitations/settings, manufacturer specification, network providerparameters/limitations, platform-specific limitations/settings, deviceOS settings, etc. In one embodiment, batch transfer can be initiatedwhen an application/window/file is closed out, exited, or moved into thebackground; users can optionally be prompted before initiating a batchtransfer; users can also manually trigger batch transfers.

In one embodiment, the local proxy 275 locally adjusts radio use on thedevice 250 by caching data in the cache 285. When requests ortransactions from the device 250 can be satisfied by content stored inthe cache 285, the radio controller 266 need not activate the radio tosend the request to a remote entity (e.g., the host server 100 as shownin FIG. 1B, the host server 400 as shown in FIG. 4A or a contentprovider/application server such as the server/provider 110 shown in theexamples of FIGS. 1B-1C). As such, the local proxy 275 can use the localcache 285 and the cache policy manager 245 to locally store data forsatisfying data requests to eliminate or reduce the use of the deviceradio for conservation of network resources and device batteryconsumption.

In leveraging the local cache, once the request/transaction manager 235intercepts a data request by an application on the device 250, the localcache repository 285 can be queried to determine if there is any locallystored response, and also determine whether the response is valid. Whena valid response is available in the local cache 285, the response canbe provided to the application on the device 250 without the device 250needing to access the cellular network or wireless broadband network.

If a valid response is not available, the local proxy 275 can query aremote proxy (e.g., the server proxy 125 of FIG. 4A) to determinewhether a remotely stored response is valid. If so, the remotely storedresponse (e.g., which may be stored on the server cache 135 or optionalcaching server 199 shown in the example of FIG. 1C) can be provided tothe mobile device, possibly without the mobile device 250 needing toaccess the cellular network, thus relieving consumption of networkresources.

If a valid cache response is not available, or if cache responses areunavailable for the intercepted data request, the local proxy 275, forexample, can send the data request to a remote proxy (e.g., server proxy125 of FIG. 4A) which forwards the data request to a content source(e.g., application server/content provider 110 of FIG. 1B), and aresponse from the content source can be provided through the remoteproxy, as will be further described in the description associated withthe example host server 400 of FIG. 4A. The cache policy manager 245 canmanage or process requests that use a variety of protocols, includingbut not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/orActiveSync. The caching policy manager 245 can locally store responsesfor data requests in the local database 285 as cache entries, forsubsequent use in satisfying same or similar data requests.

The caching policy manager 245 can request that the remote proxy monitorresponses for the data request and the remote proxy can notify thedevice 250 when an unexpected response to the data request is detected.In such an event, the cache policy manager 245 can erase or replace thelocally stored response(s) on the device 250 when notified of theunexpected response (e.g., new data, changed data, additional data,etc.) to the data request. In one embodiment, the caching policy manager245 is able to detect or identify the protocol used for a specificrequest, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP,XMPP, and/or ActiveSync. In one embodiment, application specifichandlers (e.g., via the application protocol module 248 of the cachingpolicy manager 245) on the local proxy 275 allows for optimization ofany protocol that can be port mapped to a handler in the distributedproxy (e.g., port mapped on the proxy server 125 in the example of FIG.4A).

In one embodiment, the local proxy 275 notifies the remote proxy suchthat the remote proxy can monitor responses received for the datarequest from the content source for changed results prior to returningthe result to the device 250, for example, when the data request to thecontent source has yielded same results to be returned to the mobiledevice. In general, the local proxy 275 can simulate application serverresponses for applications on the device 250, using locally cachedcontent. This can prevent utilization of the cellular network fortransactions where new/changed data is not available, thus freeing upnetwork resources and preventing network congestion.

In one embodiment, the local proxy 275 includes an application behaviordetector 236 to track, detect, observe, and/or monitor applications(e.g., proxy-aware and/or unaware applications 210 and 220) accessed orinstalled on the device 250. Application behaviors or patterns indetected behaviors (e.g., via the pattern detector 237) of one or moreapplications accessed on the device 250 can be used by the local proxy275 to optimize traffic in a wireless network needed to satisfy the dataneeds of these applications.

For example, based on detected behavior of multiple applications, thetraffic shaping engine 255 can align content requests made by at leastsome of the applications over the network (wireless network) (e.g., viathe alignment module 256). The alignment module 256 can delay orexpedite some earlier received requests to achieve alignment. Whenrequests are aligned, the traffic shaping engine 255 can utilize theconnection manager to poll over the network to satisfy application datarequests. Content requests for multiple applications can be alignedbased on behavior patterns or rules/settings including, for example,content types requested by the multiple applications (audio, video,text, etc.), device (e.g., mobile or wireless device) parameters, and/ornetwork parameters/traffic conditions, network service providerconstraints/specifications, etc.

In one embodiment, the pattern detector 237 can detect recurrences inapplication requests made by the multiple applications, for example, bytracking patterns in application behavior. A tracked pattern caninclude, detecting that certain applications, as a background process,poll an application server regularly, at certain times of day, oncertain days of the week, periodically in a predictable fashion, with acertain frequency, with a certain frequency in response to a certaintype of event, in response to a certain type user query, frequency thatrequested content is the same, frequency with which a same request ismade, interval between requests, applications making a request, or anycombination of the above, for example.

Such recurrences can be used by traffic shaping engine 255 to offloadpolling of content from a content source (e.g., from an applicationserver/content provider 110 of FIG. 1B) that would result from theapplication requests that would be performed at the mobile device orwireless device 250 to be performed instead by a proxy server (e.g.,proxy server 125 of FIG. 1C) remote from the device 250. Traffic shapingengine 255 can decide to offload the polling when the recurrences matcha rule. For example, there are multiple occurrences or requests for thesame resource that have exactly the same content, or returned value, orbased on detection of repeatable time periods between requests andresponses such as a resource that is requested at specific times duringthe day. The offloading of the polling can decrease the amount ofbandwidth consumption needed by the mobile device 250 to establish awireless (cellular or other wireless broadband) connection with thecontent source for repetitive content polls.

As a result of the offloading of the polling, locally cached contentstored in the local cache 285 can be provided to satisfy data requestsat the device 250 when content change is not detected in the polling ofthe content sources. As such, when data has not changed, applicationdata needs can be satisfied without needing to enable radio use oroccupying cellular bandwidth in a wireless network. When data haschanged and/or new data has been received, the remote entity (e.g., thehost server) to which polling is offloaded, can notify the device 250.

In one embodiment, the local proxy 275 can mitigate the need/use ofperiodic keepalive messages (heartbeat messages) to maintain TCP/IPconnections, which can consume significant amounts of power thus havingdetrimental impacts on mobile device battery life. The connectionmanager 265 in the local proxy (e.g., via the heartbeat manager 267, thekeepalive detector 305 and/or the keepalive optimizer 300) can detect,identify, and intercept any or all heartbeat (keepalive) messages beingsent from applications.

The heartbeat manager 267 can prevent any or all of these heartbeatmessages from being sent over the cellular, or other network, andinstead rely on the server component of the distributed proxy system(e.g., shown in FIG. 1C) to generate and send the heartbeat messages tomaintain a connection with the backend (e.g., applicationserver/provider 110 in the example of FIG. 1B).

In some embodiments, the radio state management engine 203 can performthe management and/or policy management of mobile device radio statepromotion or demotion based on buffer, activity and/or device statemonitoring. The radio state management engine 203 can determine whatuser activity and/or data activity should justify a radio statepromotion and communicate the information to the network to beimplemented as a single session, multi-session, or global policy. Thispolicy can be used to execute the appropriate level of throttling toprevent the radio from going to higher powered states when unjustifiedbased on dynamic conditions (e.g., network status, traffic, congestion,user expectations, user behavior, other activity, and the like.).

The local proxy 275 generally represents any one or a portion of thefunctions described for the individual managers, modules, and/orengines. The local proxy 275 and device 250 can include additional orless components; more or less functions can be included, in whole or inpart, without deviating from the novel art of the disclosure.

FIG. 2B depicts a block diagram illustrating additional components inthe local proxy shown in the example of FIG. 2A.

One embodiment of the local proxy 175 includes the user activity module215, which further includes one or more of, a user activitydetector/tracker 215 a, a user activity prediction engine 215 b, and/ora user expectation manager 215 c. The application behavior detector 236can further include a prioritization engine 241 a, a time criticalitydetection engine 241 b, an application state categorizer 241 c, and/oran application traffic categorizer 241 d. The local proxy 175 canfurther include a backlight detector 219.

In one embodiment, the application behavior detector 236 may detect,determine, identify, or infer the activity state of an application onthe mobile device 250 from which traffic has originated or is directedto, for example, via the application state categorizer 241 c and/or theapplication traffic categorizer 241 d. The activity state can bedetermined based on whether the application is in a foreground orbackground state on the mobile device (via the application statecategorizer 241 c) since the traffic for a foreground application versusa background application may be handled differently.

In one embodiment, the activity state can be determined, detected,identified, or inferred with a level of certainty of heuristics, basedon the backlight status of the mobile device 250 (e.g., by the backlightdetector 219) or other software agents or hardware sensors on the mobiledevice, including but not limited to, resistive sensors, capacitivesensors, ambient light sensors, motion sensors, touch sensors, and thelike. In general, if the backlight is on, the traffic can be treated asbeing or determined to be generated from an application that is activeor in the foreground, or the traffic is interactive. In addition, if thebacklight is on, the traffic can be treated as being or determined to betraffic from user interaction or user activity, or traffic containingdata that the user is expecting within some time frame.

In one embodiment, the activity state is determined based on whether thetraffic is interactive traffic or maintenance traffic. Interactivetraffic can include transactions from responses and requests generateddirectly from user activity/interaction with an application, and caninclude content or data that a user is waiting or expecting to receive.Maintenance traffic may be used to support the functionality of anapplication which is not directly detected by a user. Maintenancetraffic can also include actions or transactions that may take place inresponse to a user action, but the user is not actively waiting for orexpecting a response.

For example, a mail or message delete action at a mobile device 250generates a request to delete the corresponding mail or message at theserver, but the user typically is not waiting for a response. Thus, sucha request may be categorized as maintenance traffic, or traffic having alower priority (e.g., by the prioritization engine 241 a) and/or is nottime-critical (e.g., by the time criticality detection engine 241 b).

Contrastingly, a mail ‘read’ or message ‘read’ request initiated by auser at the mobile device 250, can be categorized as ‘interactivetraffic’ since the user generally is waiting to access content or datawhen they request to read a message or mail. Similarly, such a requestcan be categorized as having higher priority (e.g., by theprioritization engine 241 a) and/or as being time critical/timesensitive (e.g., by the time criticality detection engine 241 b).

The time criticality detection engine 241 b can generally determine,identify, infer the time sensitivity of data contained in traffic sentfrom the mobile device 250 or to the mobile device from a host server(e.g., host 300) or application server (e.g., app server/content source110). For example, time sensitive data can include, status updates,stock information updates, IM presence information, email messages orother messages, actions generated from mobile gaming applications,webpage requests, location updates, etc. Data that is not time sensitiveor time critical, by nature of the content or request, can includerequests to delete messages, mark-as-read or edited actions,application-specific actions such as an add-friend or delete-friendrequest, certain types of messages, or other information which does notfrequently change in nature, etc. In some instances when the data is nottime critical, the timing with which to allow the traffic to passthrough is set based on when additional data needs to be sent from themobile device 250. For example, traffic shaping engine 255 can align thetraffic with one or more subsequent transactions to be sent together ina single power-on event of the mobile device radio (e.g., using thealignment module 256 and/or the batching module 257). The alignmentmodule 256 can also align polling requests occurring close in timedirected to the same host server, since these requests are likely to beresponded to with the same data. In some instances, the timing forwithholding or delaying traffic and timing for allowing any delayed ornew traffic to the network can be based on traffic management policies.

In the alternate or in combination, the activity state can be determinedfrom assessing, determining, evaluating, inferring, identifying useractivity at the mobile device 250 (e.g., via the user activity module215). For example, user activity can be directly detected and trackedusing the user activity tracker 215 a. The traffic resulting therefromcan then be categorized appropriately for subsequent processing todetermine the policy for handling. Furthermore, user activity can bepredicted or anticipated by the user activity prediction engine 215 b.By predicting user activity or anticipating user activity, the trafficthus occurring after the prediction can be treated as resulting fromuser activity and categorized appropriately to determine thetransmission policy.

In addition, the user activity module 215 can also manage userexpectations (e.g., via the user expectation manager 215 c and/or inconjunction with the activity tracker 215 a and/or the prediction engine215 b) to ensure that traffic is categorized appropriately such thatuser expectations are generally met. For example, a user-initiatedaction should be analyzed (e.g., by the expectation manager 215 c) todetermine or infer whether the user would be waiting for a response. Ifso, such traffic should be handled under a policy such that the userdoes not experience an unpleasant delay in receiving such a response oraction.

In one embodiment, an advanced generation wireless standard network isselected for use in sending traffic between a mobile device and a hostserver in the wireless network based on the activity state of theapplication on the mobile device for which traffic is originated from ordirected to. An advanced technology standard such as the 3G, 3.5G, 3G+,4G, or LTE network can be selected for handling traffic generated as aresult of user interaction, user activity, or traffic containing datathat the user is expecting or waiting for. Advanced generation wirelessstandard networks can also be selected to transmit data contained intraffic directed to the mobile device which responds to foregroundactivities.

In categorizing traffic and defining a transmission policy for mobiletraffic, a network configuration can be selected for use (e.g., by anetwork configuration selection engine) on the mobile device 250 insending traffic between the mobile device and a proxy server and/or anapplication server (e.g., app server/host 110). The networkconfiguration that is selected can be determined based on informationgathered by the application behavior module 236 regarding applicationactivity state (e.g., background or foreground traffic), applicationtraffic category (e.g., interactive or maintenance traffic), anypriorities of the data/content, time sensitivity/criticality.

In one embodiment, the keepalive detector 305 which is described indetail with respect to FIG. 3 can also detect or identify keepalives orheartbeat messages and the keepalive optimizer 300 can use theinformation to reduce or block keepalive and other background traffic inthe mobile network

FIG. 2C depicts a block diagram illustrating additional components inthe proprietary/non-standard protocol adaptation engine shown in theexample of FIG. 2A. In one embodiment, the proprietary/non-standardprotocol adaptation engine 270 can be a part of the local proxy 275.Alternately, the proprietary/non-standard protocol adaptation engine 270can be implemented separately outside of the local proxy 275.

The proprietary/non-standard protocol adaptation engine 270 can include,for example, a transaction detection engine 272 having a protocolanalyzer 274, a transaction pattern detection engine 276, a binarymatching and normalization engine 278, an application byte streamgenerator 280, a TCP session manager 282 and/or a protocolencoding/decoding module 284. Additional or less modules/engines can beincluded. The various components of the proprietary/non-standardprotocol adaptation engine 401 on the mobile device or user equipment(UE) 250 can singularly or in any combination perform the followingfunctions and features related to signaling optimization in a wirelessnetwork for traffic utilizing proprietary and nonproprietary protocols.

In one embodiment, the local proxy 275 or the proprietary/non-standardprotocol adaptation engine 401 captures the TCP stream from anapplication and passes it on as a byte stream via a byte streaminterface provided by the application byte stream generator 280. A bytestream can be read from or can be written to by an application or clientwithout having to account for protocol-specific formatting, sizing, andother details.

The TCP session manager 282 can, in one embodiment, manage TCP sessionsincluding establishing of TCP sessions with a proxy server (e.g., proxyserver 125) and/or the content server (e.g., content server 110) andtearing down or termination of TCP sessions. Although the discussion iswith respect to TCP sessions, other similar or session-based protocolsmay be implemented. In one implementation, the TCP session manager 282can establish a first TCP session between an application and the localproxy 275 or the proprietary/non-standard protocol adaptation engine270. The TCP session manager 282 can also establish a TCP sessionbetween the local proxy 275 (or the proprietary/non-standard protocoladaptation engine 270) and a server (e.g., proxy server 125, anapplication or content server 110). Byte streams from the applicationcan be passed over the first TCP session to the keepalive detector 305and/or the keepalive optimizer 300, which can then be sent over to theserver over the second TCP session. The TCP session manager 282 may alsoallow the application to establish the necessary handshakes.

In one embodiment, the transaction detection engine 272 can detect andidentify transactions based on analysis of the protocol headers andother protocol peculiarities. Such protocol specific analysis can beperformed by a protocol analyzer 274. For example, the protocol analyzer274 can detect transactions in HTTP protocol based on HTTP header,formatting, encoding, and the like.

In another embodiment, the transaction detection engine 272 can beprotocol agnostic, and can detect and/or identify transactions withoutknowing or understanding details of the underlying protocols. Forexample, the transaction detection engine 272 can directly monitor bytestreams captured from applications (e.g., by the application byte streamgenerator 280 interface) and detect and/or identify transactions basedon observed and/or extracted patterns of byte streams and/or matching ordetermining content in byte streams. In one implementation, for example,the transaction pattern detection engine 276 can monitor, detect and/orextract various patterns embedded in byte streams corresponding totransactions from applications. One such pattern can be idle timebetween transactions. The pattern detection engine 276 can monitor bytestreams from an application over time, and detect an idle time of twominutes occurring in between transactions, without knowing orunderstanding the details of the protocol used by the application. Otherpatterns that can be identified or extracted can resemble thoseidentified by the distributed proxy system (e.g., the local proxy 275and/or the proxy server 125) for HTTP or other standard protocols.

In one embodiment, the proprietary/non-standard protocol adaptationengine 401 can include a protocol encoding/decoding module 284. Inimplementations where a binary stream is encapsulated within a securityand/or encryption protocol such as Transport Layer Security (TLS),Secure Sockets Layer (SSL), and the like, the encoding/decoding modulemay include capabilities for decoding such protocols to extract thebinary stream.

FIG. 3 depicts a block diagram illustrating additional components in thekeepalive detector 305 shown in the example of FIG. 2A. In someembodiments, the keepalive detector 305 can include a network log dataanalyzer 310 having a regular keepalive interval detector 315 and aregular keepalive byte size detector 315 and a keepalive reporter 335.In some other embodiments, the keepalive detector 305 can include aconnection analyzer 320 having a connection object creator/updatormodule 325 and a connection object mapping module 330 and a keepalivereporter 335. In yet other embodiments, the keepalive detector caninclude the network log data analyzer 310, the connection analyzer 320and the keepalive reporter 335.

The network log data analyzer 310 can examine patterns of data sent fromand received by a mobile application on a mobile device. Such patternsof data sent from and received by the mobile application can havevariable intervals and sizes which introduce ambiguities regardingwhether such data are related to keepalives or not. In order to removethe ambiguities, the network log data analyzer 310 can use the regularkeepalive interval detector 315 and the regular keepalive byte sizedetector 318 to perform statistical analyses on the patterns of datasent from and received by the mobile application to detect a patternthat is regular and to detect regular byte sizes respectively. Thenetwork log data analyzer 310 can then identify the keepalives from theTCP stream occurring over the same TCP session based on informationrelating to the pattern that is detected as regular and the regular bytesizes.

In some embodiments, the regular keepalive interval detector 315 candetect the pattern as regular when (1) the pattern occurs more than aminimum number of times during a duration (e.g., more than 5 times anhour); (2) intervals between occurrences of the pattern is distributedsuch that a difference between an interval in a first quartile and aninterval in a third quartile is within a threshold percentage of amedian of the intervals or a variance of intervals between a thresholdnumber of sequential occurrences of the pattern is less than a maximumthreshold as determined by the regular keepalive interval detector 315;and (3) the pattern's median of the intervals is greater than a minimumthreshold. In some embodiments, all three conditions need not besatisfied for the pattern to be detected as regular.

The regular keepalive byte size detector 318 can detect the regular bytesizes when when patterns including same sizes of data sent from andreceived by the mobile application, same sizes of data sent from themobile application or same sizes of data received by the mobileapplication are detected as regular. In further embodiments, the regularbyte size can be detected by the detector 318 by performing a clusteranalysis to identify patterns including data sent from and received bythe mobile application, data sent from the mobile application or datareceived by the mobile application having a variance in sizes that isless than a threshold that are detected as regular. The logic flowdiagrams of FIGS. 5-8 describe various aspects of the network log dataanalyzer 310 and its components.

The connection analyzer 320 can, in some embodiments, detect keepalivesor network transactions from stream data on a mobile device. Theconnection analyzer 320 can detect a message including stream data for asocket. Based on information in the message, the connection objectcreator/updator 325 can determine whether to create or update aconnection object. For example, the connection object creator/updator325 can analyze the message to determine time the socket was created andcreate the connection object when the socket was created was more thanan amount of given time ago. Similarly, the connection objectcreator/updator 325 can analyze the message to determine the informationincluding an amount of data transferred from a client to a server andfrom the server to the client and timing characteristics and update theconnection object when the amount of data transferred is less than athreshold amount and the timing characteristics indicates that a timeinterval since the last data transfer event occurred more than athreshold interval.

The connection object is associated with a data structure that includesan identifier for the connection object, time the socket was created, akeepalive weight that is initialized to a value on creation of theconnection object and incremented each time the connection object isupdated, a flag for indicating whether the keepalive was detected and aflag indicating whether the message contains a keepalive. The connectionobject including the associated data structure can be stored in thelocal cache 340 or the persistent local storage 345. The connectionobject creator/updator 325 can further evaluate the connection object todetermine whether a keepalive is detected and update the correspondingflag in the keepalive data structure. The evaluation can includeevaluating the keepalive weight of the connection object upon updatingthe connection object to determine whether the keepalive weight ishigher than a threshold.

The keepalive reporter 335 can report changes to the connection objectincluding a formatted form of the data structure to the server.

In some embodiments, the keepalive detector 305 can identify networktransactions (e.g., keepalives) from a Transport Control Protocol (TCP)stream by obtaining one or more network transaction parametersdetermined from examination of patterns of data sent from and receivedby a mobile application on a mobile device and identifying the networktransactions from the TCP stream based on the one or more networktransaction parameters. The network transactions occur over the same TCPsession and are proxy streamed. In some embodiments, the one or morenetwork transaction parameters include a regular interval, a regularsize threshold that is determined from the patterns of data sent fromand received by the mobile application based on statistical analysis,similar or repeating content within the patterns of data sent from andreceived by the mobile application, content following a certain patternor a combination thereof. The repeating content in the networktransactions can have parts or portions that are the same or can havesome portions that follow a pattern (e.g., a counter or incrementing ordecrementing pattern, time stamp). In some embodiments, the patterns ofdata sent from and received by the mobile application are recorded in anetwork communication log along with patterns of data sent from andreceived by other mobile applications on the mobile device. The networktransaction parameters can be determined locally on the mobile device(e.g., via the network log data analyzer 310) or remotely on a proxyserver (e.g., via the network log data analyzer 430).

FIG. 4A depicts a block diagram illustrating an example of server-sidecomponents in a distributed proxy and cache system, further including akeepalive detector that can identify keepalives from a TCP stream and aproprietary/non-standard protocol adaptation engine. In someembodiments, the server-side proxy (or proxy server 125) can furthercategorize mobile traffic and/or deploy and/or implement policies suchas traffic management and delivery policies based on device state,application behavior, content priority, user activity, and/or userexpectations.

The host server 400 generally includes, for example, a network interface408 and/or one or more repositories 412, 414, and 416. Note that server400 may be any portable/mobile or non-portable device, server, clusterof computers and/or other types of processing units (e.g., any number ofa machine shown in the example of FIG. 1B) able to receive or transmitsignals to satisfy data requests over a network including any wired orwireless networks (e.g., Wi-Fi, cellular, Bluetooth, etc.).

The network interface 408 can include networking module(s) or devices(s)that enable the server 400 to mediate data in a network with an entitythat is external to the host server 400, through any known and/orconvenient communications protocol supported by the host and theexternal entity. Specifically, the network interface 408 allows theserver 400 to communicate with multiple devices including mobile phonedevices 450 and/or one or more application servers/content providers410.

The host server 400 can store information about connections (e.g.,network characteristics, conditions, types of connections, etc.) withdevices in the connection metadata repository 412. Additionally, anyinformation about third-party applications or content providers can alsobe stored in the repository 412. The host server 400 can storeinformation about devices (e.g., hardware capability, properties, devicesettings, device language, network capability, manufacturer, devicemodel, OS, OS version, etc.) in the device information repository 414.Additionally, the host server 400 can store information about networkproviders and the various network service areas in the network serviceprovider repository 416.

The communication enabled by network interface 408 allows forsimultaneous connections (e.g., including cellular connections) withdevices 450 and/or connections (e.g., including wired/wireless, HTTP,Internet connections, LAN, WiFi, etc.) with content servers/providers410 to manage the traffic between devices 450 and content providers 410,for optimizing network resource utilization and/or to conserver power(battery) consumption on the serviced devices 450. The host server 400can communicate with mobile devices 450 serviced by different networkservice providers and/or in the same/different network service areas.The host server 400 can operate and is compatible with devices 450 withvarying types or levels of mobile capabilities, including by way ofexample but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G(IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 5G (IMT-advanced), etc.

In general, the network interface 408 can include one or more of anetwork adaptor card, a wireless network interface card (e.g., SMSinterface, WiFi interface, interfaces for various generations of mobilecommunication standards including but not limited to 1G, 2G, 3G, 3.5G,5G type networks such as LTE, WiMAX, etc.), Bluetooth, WiFi, or anyother network whether or not connected via a router, an access point, awireless router, a switch, a multilayer switch, a protocol converter, agateway, a bridge, a bridge router, a hub, a digital media receiver,and/or a repeater.

The host server 400 can further include server-side components of thedistributed proxy and cache system which can include a proxy server 125and a server cache 435. In some embodiments, the proxy server 125 caninclude an HTTP access engine 445, a caching policy manager 455, a proxycontroller 465, a traffic shaping engine 475, a new data detector 447and/or a connection manager 495.

The HTTP access engine 445 may further include a heartbeat manager 498;the proxy controller 465 may further include a data invalidator module468; the traffic shaping engine 475 may further include a controlprotocol 476 and a batching module 477. Additional or lesscomponents/modules/engines can be included in the proxy server 125 andeach illustrated component.

In the example of a device (e.g., mobile device 450) making anapplication or content request to an application server or contentprovider 410, the request may be intercepted and routed to the proxyserver 125 which is coupled to the device 450 and the applicationserver/content provider 410. Specifically, the proxy server is able tocommunicate with the local proxy (e.g., proxy 175 of the examples ofFIG. 1C) of the mobile device 450, the local proxy forwards the datarequest to the proxy server 125 in some instances for further processingand, if needed, for transmission to the application server/contentserver 410 for a response to the data request.

In such a configuration, the host 400, or the proxy server 125 in thehost server 400 can utilize intelligent information provided by thelocal proxy in adjusting its communication with the device in such amanner that optimizes use of network and device resources. For example,the proxy server 125 can identify characteristics of user activity onthe device 450 to modify its communication frequency. Thecharacteristics of user activity can be determined by, for example, theactivity/behavior awareness module 466 in the proxy controller 465 viainformation collected by the local proxy on the device 450.

In some embodiments, communication frequency can be controlled by theconnection manager 495 of the proxy server 125, for example, to adjustpush frequency of content or updates to the device 450. For instance,push frequency can be decreased by the connection manager 495 whencharacteristics of the user activity indicate that the user is inactive.In some embodiments, when the characteristics of the user activityindicate that the user is subsequently active after a period ofinactivity, the connection manager 495 can adjust the communicationfrequency with the device 450 to send data that was buffered as a resultof decreased communication frequency to the device 450.

In addition, the proxy server 125 includes priority awareness of variousrequests, transactions, sessions, applications, and/or specific events.Such awareness can be determined by the local proxy on the device 450and provided to the proxy server 125. The priority awareness module 467of the proxy server 125 can generally assess the priority (e.g.,including time-criticality, time-sensitivity, etc.) of various events orapplications; additionally, the priority awareness module 467 can trackpriorities determined by local proxies of devices 450.

In some embodiments, through priority awareness, the connection manager495 can further modify communication frequency (e.g., use or radio ascontrolled by the radio controller 496, Internet/Wi-Fi Controller 497)of the server 400 with the devices 450. For example, the server 400 cannotify the device 450, thus requesting use of the radio if it is notalready in use when data or updates of an importance/priority levelwhich meets a criteria becomes available to be sent.

In some embodiments, the proxy server 125 can detect multipleoccurrences of events (e.g., transactions, content, data received fromserver/provider 410) and allow the events to accumulate for batchtransfer to device 450. Batch transfer can be cumulated and transfer ofevents can be delayed based on priority awareness and/or useractivity/application behavior awareness as tracked by modules 467 and/or466. For example, batch transfer of multiple events (of a lowerpriority) to the device 450 can be initiated by the batching module 477when an event of a higher priority (meeting a threshold or criteria) isdetected at the server 400. In addition, batch transfer from the server400 can be triggered when the server receives data from the device 450,indicating that the device radio is already in use and is thus on. Insome embodiments, the proxy server 125 can order the eachmessages/packets in a batch for transmission based on event/transactionpriority such that higher priority content can be sent first in caseconnection is lost or the battery dies, etc.

In some embodiments, the server 400 caches data (e.g., as managed by thecaching policy manager 455) such that communication frequency over anetwork (e.g., cellular network) with the device 450 can be modified(e.g., decreased). The data can be cached, for example, in the servercache 435 for subsequent retrieval or batch sending to the device 450 topotentially decrease the need to turn on the device 450 radio. Theserver cache 435 can be partially or wholly internal to the host server400, although in the example of FIG. 4 it is shown as being external tothe host 400. In some instances, the server cache 435 may be the same asand/or integrated in part or in whole with another cache managed byanother entity (e.g., the optional caching proxy server 199 shown in theexample of FIG. 1C), such as being managed by an applicationserver/content provider 410, a network service provider, or anotherthird party.

In some embodiments, content caching is performed locally on the device450 with the assistance of host server 400. For example, proxy server125 in the host server 400 can query the application server/provider 410with requests and monitor changes in responses. When changed or newresponses are detected (e.g., by the new data detector 447), the proxyserver 125 can notify the mobile device 450 such that the local proxy onthe device 450 can make the decision to invalidate (e.g., indicated asoutdated) the relevant cache entries stored as any responses in itslocal cache. Alternatively, the data invalidator module 468 canautomatically instruct the local proxy of the device 450 to invalidatecertain cached data, based on received responses from the applicationserver/provider 410. The cached data is marked as invalid, and can getreplaced or deleted when new content is received from the content server410.

Note that data change can be detected by the detector 447 in one or moreways. For example, the server/provider 410 can notify the host server400 upon a change. The change can also be detected at the host server400 in response to a direct poll of the source server/provider 410. Insome instances, the proxy server 125 can, in addition, pre-load thelocal cache on the device 450 with the new/updated data. This can beperformed when the host server 400 detects that the radio on the mobiledevice is already in use, or when the server 400 has additionalcontent/data to be sent to the device 450.

One or more the above mechanisms can be implemented simultaneously oradjusted/configured based on application (e.g., different policies fordifferent servers/providers 410). In some instances, the sourceprovider/server 410 may notify the host 400 for certain types of events(e.g., events meeting a priority threshold level). In addition, theprovider/server 410 may be configured to notify the host 400 at specifictime intervals, regardless of event priority.

In some embodiments, the proxy server 125 of the host 400 canmonitor/track responses received for the data request from the contentsource for changed results prior to returning the result to the mobiledevice; such monitoring may be suitable when data request to the contentsource has yielded same results to be returned to the mobile device,thus preventing network/power consumption from being used when no newchanges are made to a particular requested. The local proxy of thedevice 450 can instruct the proxy server 125 to perform such monitoringor the proxy server 125 can automatically initiate such a process uponreceiving a certain number of the same responses (e.g., or a number ofthe same responses in a period of time) for a particular request.

In some embodiments, the server 400, through the activity/behaviorawareness module 466, is able to identify or detect user activity at adevice that is separate from the mobile device 450. For example, themodule 466 may detect that a user's message inbox (e.g., email or typesof inbox) is being accessed. This can indicate that the user isinteracting with his/her application using a device other than themobile device 450 and may not need frequent updates, if at all.

The server 400, in this instance, can thus decrease the frequency withwhich new or updated content is sent to the mobile device 450, oreliminate all communication for as long as the user is detected to beusing another device for access. Such frequency decrease may beapplication specific (e.g., for the application with which the user isinteracting on another device), or it may be a general frequencydecrease (e.g., since the user is detected to be interacting with oneserver or one application via another device, he/she could also use itto access other services) to the mobile device 450.

In some embodiments, the host server 400 is able to poll content sources410 on behalf of devices 450 to conserve power or battery consumption ondevices 450. For example, certain applications on the mobile device 450can poll its respective server 410 in a predictable recurring fashion.Such recurrence or other types of application behaviors can be trackedby the activity/behavior module 466 in the proxy controller 465. Thehost server 400 can thus poll content sources 410 for applications onthe mobile device 450 that would otherwise be performed by the device450 through a wireless (e.g., including cellular connectivity). The hostserver can poll the sources 410 for new or changed data by way of theHTTP access engine 445 to establish HTTP connection or by way of radiocontroller 496 to connect to the source 410 over the cellular network.When new or changed data is detected, the new data detector 447 cannotify the device 450 that such data is available and/or provide thenew/changed data to the device 450.

In some embodiments, the connection manager 495 determines that themobile device 450 is unavailable (e.g., the radio is turned off) andutilizes SMS to transmit content to the device 450, for instance, viathe SMSC 162 shown in the example of FIG. 1C. SMS is used to transmitinvalidation messages, batches of invalidation messages, or even contentin the case where the content is small enough to fit into just a few(usually one or two) SMS messages. This avoids the need to access theradio channel to send overhead information. The host server 400 can useSMS for certain transactions or responses having a priority level abovea threshold or otherwise meeting a criteria. The server 400 can alsoutilize SMS as an out-of-band trigger to maintain or wake-up an IPconnection as an alternative to maintaining an always-on IP connection.

In some embodiments, the connection manager 495 in the proxy server 125(e.g., the heartbeat manager 498) can generate and/or transmit heartbeatmessages on behalf of connected devices 450 to maintain a backendconnection with a provider 410 for applications running on devices 450.

For example, in the distributed proxy system, local cache on the device450 can prevent any or all heartbeat messages needed to maintain TCP/IPconnections required for applications from being sent over the cellular,or other, network and instead rely on the proxy server 125 on the hostserver 400 to generate and/or send the heartbeat messages to maintain aconnection with the backend (e.g., application server/provider 110 inthe example of FIG. 1B). The proxy server can generate the keepalive(heartbeat) messages independent of the operations of the local proxy onthe mobile device.

The repositories 412, 414, and/or 416 can additionally store software,descriptive data, images, system information, drivers, and/or any otherdata item utilized by other components of the host server 400 and/or anyother servers for operation. The repositories may be managed by adatabase management system (DBMS), for example, which may be but is notlimited to Oracle, DB2, Microsoft Access, Microsoft SQL Server,PostgreSQL, MySQL, FileMaker, etc.

The repositories can be implemented via object-oriented technologyand/or via text files and can be managed by a distributed databasemanagement system, an object-oriented database management system(OODBMS) (e.g., ConceptBase, FastDB Main Memory Database ManagementSystem, JDOlnstruments, ObjectDB, etc.), an object-relational databasemanagement system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS,etc.), a file system, and/or any other convenient or known databasemanagement package.

In one embodiment, the keepalive or heartbeat manager 490 can determinewhether to continue or disconnect the TCP session with the contentserver to allow the content server to determine the correct status ofthe user/mobile device based the keepalives received or not receivedfrom the local proxy 175 or the mobile device. For example, if thekeepalive manager 490 receives no keepalive when expected, the keepalivemanager can terminate the session with the content server to enable thecontent server to determine the correct status of the user/mobiledevice.

In some embodiments, the proxy server 125 includes a keepalive detector405 and/or a proprietary/non-standard protocol adaptation engine 470.FIG. 4B depicts a block diagram illustrating additional components inthe keepalive detector shown in the example of FIG. 4A. The keepalivedetector 405 can include a network log data analyzer 430 having aregular keepalive interval detector 432 and a regular keepalive bytesize detector 434. These modules can perform same/similar functions asthe corresponding modules described in reference to FIG. 3. Thekeepalive detector 405 can also include a keepalive parameters module436 which can maintain keepalive parameters such as regular interval andbyte sizes for mobile applications. These keepalive parameters can thenbe pushed to mobile devices for assistance in detecting keepalives orother network transactions.

FIG. 4C depicts a block diagram illustrating additional components inthe proprietary/non-standard protocol adaptation engine shown in theexample of FIG. 4A.

Referring to FIG. 3B, the proprietary/non-standard protocol adaptationengine 470 can include, for example, a transaction detection engine 471having a protocol analyzer 472, transaction pattern detection engine 473and a binary matching and normalization engine 474, an application bytestream generator 480, a session manager 482, and/or a protocolencoding/decoding module 484. Additional or less modules/engines can beincluded.

The various components of the proprietary/non-standard protocoladaptation engine 470 on the remote proxy or proxy server 125 cansingularly or in any combination perform the above described functionsand features related to signaling optimization in a wireless network fortraffic utilizing proprietary and non-proprietary protocols. The variouscomponents of the proprietary/non-standard protocol adaptation engine470 can also alone or in combination perform the above describedfunctions with the mobile device or user equipment (UE) side component(e.g., the local proxy 275 and/or the proprietary/non-standard protocoladaptation engine 270 related to optimize signaling in a wirelessnetwork for traffic utilizing proprietary (non-standard) andnon-proprietary (standard) protocols.

In one embodiment, many of the example components of theproprietary/non-standard protocol adaptation engine 470 on the proxyserver can perform similar/same functions as the example components ofthe proprietary/non-standard protocol adaptation engine 270 on the localproxy. For example, the engine 470 can capture data for an applicationreceived from the content server. In one implementation, the applicationbyte stream generator 480 can also provide a similar byte streaminterface to capture data stream from the content server without havingto understand the details of the protocol used.

The session manager 482 can, in one embodiment, manage TCP sessionincluding establishing of TCP sessions with the content server and thelocal proxy and tearing down of TCP sessions. Although the discussion iswith respect to TCP, other similar or session based protocols may beimplemented. Byte streams from the content server can be passed over tothe local proxy via the TCP sessions. The session manager 482 may alsocoordinate the establishment of necessary handshakes between theapplication and the content server.

In one embodiment, the transaction detection engine 473 can detect andidentify transactions based on analysis of the protocol headers andother protocol peculiarities. Such protocol specific analysis can beperformed by a protocol analyzer 472. For example, the protocol analyzer472 can detect transactions in HTTP protocol based on HTTP header. Inanother embodiment, the transaction detection engine 471 can be protocolagnostic, and can detect and/or identify transactions without knowing orunderstanding the underlying protocols. For example, the transactiondetection engine 471 can detect and/or identify transactions based onobserved and/or extracted patterns and/or content matching. In oneimplementation, for example, a pattern detection engine 473 can detectand/or extract various patterns or change in patterns embedded in bytestreams corresponding to transactions from applications and/or clientserver. One such pattern can be idle time between transactions. Thepattern detection engine can monitor byte streams from anapplication/client server over time, and detect an idle time of twominutes occurring in between transactions. The detection can occurwithout any protocol-specific understanding of the binary streamcomprising the transaction. Various other patterns as described withrespect to the proprietary/non-standard protocol adaptation engine 401can be identified or extracted.

In one embodiment, the binary matching and normalization engine 474 cananalyze content in byte streams to determine content similarity. Thecontent similarity can be established by exact or fuzzy binary matchesand binary-level normalizations can be applied to accommodateprotocol-specificities, when determined. The transaction patterndetection engine 473 can also detect any change in the transactionpattern by using binary matching and normalization engine 474 in someembodiments. In one implementation, content of a byte stream from anapplication can be matched with content of byte stream corresponding tothe identified pattern to determine whether the two contents are thesame, similar, or approximately the same (e.g., same content but withdifferent time stamp, increment factor, a random portion, etc.). Basedon the result of the comparison, the transaction pattern detectionengine 473 can determine whether there is a change in the pattern, andif so, the engine can alert or signal the session manager 482 toestablish or re-establish a session with the local proxy to deliver thechanged content received from the content server to the application viathe local proxy.

In one embodiment, the proprietary/non-standard protocol adaptationengine 470 can include a protocol encoding/decoding module 484. Inimplementations where a binary stream is encapsulated within a securityand/or encryption protocol such as Transport Layer Security (TLS),Secure Sockets Layer (SSL), and the like, the encoding/decoding modulemay include capabilities for decoding such protocols to extract thebinary stream.

FIG. 5 depicts a logic flow diagram illustrating an example method 500of analyzing socket level network communication log data usingstatistical analyses to identify regular interval and regular byte sizescorresponding of keepalives originating from an application. In theexample method 500, a keepalive detector (e.g., keepalive detector 305or the keepalive detector 405) examines socket level networkcommunication log data. The log data can include information relating tobytes sent and received by multiple different applications or clients ona mobile device in some embodiments. The log data is examined on a perapplication basis. At block 510, the keepalive detector performs astatistical analysis on the log data corresponding to an application todetermine a regular interval for a pattern of data sent from andreceived by that application. Referring to FIG. 6, an example method 600of performing the statistical analysis on the bytes sent from andreceived by the application to determine a regular keepalive interval isdescribed.

In the example method 600, the keepalive detector (e.g., the regularkeepalive interval detector 432) examines the pattern of data sent andreceived by the application at block 605. The keepalive detector thendetermines if the pattern occurs more than a threshold (x) number oftimes in a given duration (e.g., more than 15 times per day) at decisionblock 615. If false, no regular interval can be detected and the methodterminates at block 630. The method can be rerun once more data islogged. If true, the keepalive detector determines whether the intervaltime for the pattern is uniform at decision block 615. The interval timecan be considered to be uniform if the interval times distributed closetogether. For example, if the 1^(st) quartile and 3^(rd) quartiledifference is smaller than a median interval threshold, the interval canbe considered uniform. Alternately, without looking at 1^(st) or 3^(rd)quartiles, the pattern can be considered uniform if the pattern containsa sequence of a threshold number of bytes sent and received whoseintervals' variance is smaller than a threshold. For example, if thepattern contains a sequence of 3 bytes sent and received and thevariance of the intervals between the bytes sent and received is lessthan 0.1, the pattern is considered to be uniform. If the pattern has nouniform interval time, the keepalive detector can terminate the methodat block 630 without detecting a regular interval. Conversely, if thepattern has a uniform interval time, then the keepalive detector candetermine if the median interval time for the pattern is greater than athreshold amount of time at decision block 620. If false, no regularinterval can be detected and the method terminates at block 630. Iftrue, a regular interval for the pattern is detected at block 625.

Referring to FIG. 5, at block 515, the keepalive detector performsstatistical analysis on the log data corresponding to the application todetermine a regular byte size of keepalives originating from thatapplication. An example method of performing the statistical analysis isdescribed in detail in FIG. 7. In the example method 700, the keepalivedetector (e.g., keepalive regular byte size detector) examines thepattern of data sent and received at block 705. At decision block 710,the keepalive detector determines if the same sized data is sent andreceived regularly (i.e., if the pattern comprises the same sized datasent and received (e.g., 8 fromapp bytes and 10 fromnet bytes) at a“regular” interval as defined in the example method of FIG. 6). If true,the byte sizes of the data sent and received are detected as the regularbyte sizes for the pattern at block 765. If false, the keepalivedetector determines if the same sized data is sent regularly (i.e., inregular intervals as defined in the example method of FIG. 6) atdecision block 715. If the same sized data is sent regularly, thekeepalive detector detects the byte size of the data sent as a regularbyte size for data sent at block 720. Conversely, if the same sized datais not sent regularly, the keepalive detector can determine if the samesized data is received regularly at decision block 725. If true, thekeepalive detector detects the byte size of the data received as aregular byte size for received data. at block 730. If false, thekeepalive detector applies a clustering algorithm to cluster similarsized data sent and received in the pattern at block 735. The keepalivedetector then determines if the variance of the cluster of data sent andreceived is less than a threshold and if the pattern is a regularpattern (i.e., has a regular interval) at decision block 740. If true,the keepalive detector detects the pattern as having regular byte sizesat block 765. If false, the keepalive detector determines if thevariance of the cluster of data sent is less than a threshold and if thepattern is a regular pattern at decision block 745. If true, thekeepalive detector detects that the regular byte sizes for the patternat block 750. If false, the keepalive detector again performs ananalysis of the variance of the cluster of data received in the patternto determine if the variance is less than a threshold and if the patternoccurs regularly at decision block 755. If true, the keepalive detectordetects a regular byte size pattern at block 730. If false, thekeepalive detector terminates the method at block 760 without detectinga regular byte size pattern. Referring to FIG. 5, the method 500 canstore the regular byte sizes and regular intervals as keepaliveparameters in association with the application such that the keepaliveparameters can be used in detecting keepalives.

For example, FIG. 8 depicts a logic flow diagram illustrating an examplemethod of monitoring a TCP stream of data sent and received by theapplication and identifying keepalives from the TCP stream when the sameTCP stream includes regular byte sized data sent and received at regularintervals. In the example method 800, the keepalive detector monitorsdata sent from and/or received by the application at block 810. Thekeepalive detector, at decision block 810, determines if the data sentand/or received have a regular interval and regular byte size pattern.In some embodiments, the determination can include comparing theinterval and byte size pattern to the stored keepalive parametersdetermined for the application to determine if there is a match or ifthe values are similar (e.g., within a threshold such as +/−5%). Inother embodiments, the keepalive detector can collect enough data toperform the statistical analysis associated with determining that thepattern of data has a regular interval and regular byte sizes. If thedata sent and/or received have a regular interval and regular bytesizes, the keepalive detector determines the data sent and/or receivedoccurred over the same TCP session and were proxy streamed at decisionblock 815. If true, the keepalive detector detects the data sent and/orreceived as keepalive traffic at block 820. Conversely, at decisionblock 810, if no regular interval and/or regular byte sizes was detectedor the data was not sent or received over the same TCP session or thedata was not proxy streamed, the keepalive detector does not detect anykeepalive traffic at block 825.

FIG. 9 depicts a logic flow diagram illustrating an example method ofusing timing characteristics and an amount of data sent and received toidentify whether a connection or TCP stream contains a keepalive andreporting the detection of the keepalive. In the example method 900, thekeepalive detector (e.g., connection analyzer) monitors TDR messages atblock 905. The keepalive detector detects a TDR message including aconnection ID at block 910. The keepalive detector then searches for aconnection object in a connections map that has a matching connection IDat block 915. If a matching connection object is not found at decisionblock 920, the keepalive detector creates a new connection object withinformation from the TDR message and initializes a keepalive weightassociated with the object to 1 at block 925. The keepalive detectorthen inserts the connection object to the connections map using theconnection ID at block 930.

Conversely, if a matching connection object is found at decision block920, the keepalive detector determines if the amount of data sent and/orreceived is less than a threshold at decision block 935. If true, thekeepalive detector determines if the time since the last data transferis greater than a threshold at decision block 940. If true, thekeepalive detector updates the connection object by incrementing thekeepalive weight of the connection object by 1 at block 945. Thekeepalive detector then determines if the keepalive weight is greaterthan a threshold (e.g., 3) at decision block 950. If true, the keepalivedetector confirms detection of a keepalive at block 955. The keepalivedetector then updates the connection object by updating a flag toindicate a keepalive detected status. The keepalive detector thenreports changes to the connection object including the keepalivedetected status and the keepalive weight to a proxy server 125 or a hostserver (e.g., host server 100). In the case in which the keepaliveweight is less than the threshold at decision block 950, the keepalivedetector cannot confirm that the TDR message includes a keepalive, butthe keepalive detector can still report changes in the connection objectto the proxy server or the host server.

FIG. 10 depicts a diagrammatic representation of a machine in theexample form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

In the example of FIG. 10, the computer system 1000 includes aprocessor, memory, non-volatile memory, and an interface device. Variouscommon components (e.g., cache memory) are omitted for illustrativesimplicity. The computer system 1000 is intended to illustrate ahardware device on which any of the components depicted in the exampleof FIGS. 2A-2C, FIG. 3 and FIGS. 4A-4C (and any other componentsdescribed in this specification) can be implemented. The computer system1000 can be of any applicable known or convenient type. The componentsof the computer system 1000 can be coupled together via a bus or throughsome other known or convenient device.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 1000. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, for large programs, it may not even be possible to storethe entire program in the memory. Nevertheless, it should be understoodthat for software to run, if necessary, it is moved to a computerreadable location appropriate for processing, and for illustrativepurposes, that location is referred to as the memory in this paper. Evenwhen software is moved to the memory for execution, the processor willtypically make use of hardware registers to store values associated withthe software, and local cache that, ideally, serves to speed upexecution. As used herein, a software program is assumed to be stored atany known or convenient location (from non-volatile storage to hardwareregisters) when the software program is referred to as “implemented in acomputer-readable medium.” A processor is considered to be “configuredto execute a program” when at least one value associated with theprogram is stored in a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system. The interface can include an analogmodem, ISDN modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 12 residein the interface.

In operation, the computer system 1000 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are at times shown as being performed inseries, these processes or blocks may instead be performed in parallel,or may be performed at different times. Further any specific numbersnoted herein are only examples: alternative implementations may employdiffering values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system may varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. §112, ¶16, other aspects may likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claims intended to be treated under 35U.S.C. §112, ¶16 will begin with the words “means for”.) Accordingly,the applicant reserves the right to add additional claims after filingthe application to pursue such additional claim forms for other aspectsof the disclosure.

What is claimed is:
 1. A method of identifying keepalives from aTransport Control Protocol (TCP) stream, comprising: examining patternsof data sent from and received by a mobile application on a mobiledevice, wherein the patterns have variable intervals and sizes;performing statistical analyses on the patterns of data sent from andreceived by the mobile application to detect a pattern that is regularand to detect regular byte sizes; and identifying the keepalives fromthe TCP stream occurring over the same TCP session based on informationrelating to the pattern that is detected as regular and the regular bytesizes.
 2. A method comprising: detecting inactivity of a user at amobile device; entering a power save mode on the mobile device based onthe detected inactivity; altering behavior of background activities fromapplications executing on the mobile device while in the power savemode.